How We Cut Intercompany Payment Processing Time by 65% With a Simple XML Workflow

Each intercompany (IC) cycle followed a familiar pattern. The files would come in, the teams would prepare, and then the real work would begin. Manually setting up payments, one by one, inside Cobase was the standard. 

For a process that runs regularly and at scale, it was surprisingly manual. 

Across entities in the US, UK, and Netherlands, most IC payments required full manual setup. Only a small subset mainly domestic EFT payments within Netherlands and Germany were automated. Everything else depended on the Accounts Payable (AP) team building payment instructions line by line. 

The result? A predictable operational bottleneck. Every single cycle.

The Time Was Adding Up Quietly 

On paper, the process worked. Payments went through. Reconciliations followed. Nothing was “broken.” 

But when we looked closer, the cost became clear: 

• The AP team spent 4 to 4.5 hours per IC run setting up and reviewing payments 
• The GL team spent nearly 3 hours preparing, validating, and coordinating the IC payment file 
• Most of this time was spent on manual input, verification, and back-and-forth checks 

That’s 7+ hours of combined effort per cycle, largely tied up in repetitive work. 

And during peak IC weeks, when volumes were highest, that effort scaled linearly. More transactions meant more manual setup, more review, and more room for delays or errors. 

Where the Process Was Breaking Down 

When we mapped the workflow end-to-end, a few clear friction points emerged: 

1. Manual Payment Setup in Cobase: Each payment had to be entered individually, increasing both workload and dependency on accuracy at the point of entry. 

2. High Volume, Low Leverage Work: IC cycles involve large batches of transactions, but the process didn’t take advantage of that. There was no real bulk-processing capability. 

3. Repetitive Validation and Review: Even after setup, every payment required careful review, adding another layer of time and effort. 

Individually, these steps made sense. Together, they created a system that was reliable—but inefficient. 

The Question That Changed the Approach 

At a certain point, the problem wasn’t whether the process worked. It was whether it worked well enough. 

Instead of optimizing individual steps, we asked a simpler question: 

What if we removed the need for manual entry altogether?

The Solution: XML-Based Bulk Payment Uploads 

Rather than continuing with manual inputs inside Cobase, we shifted the process upstream. This was done by preparing structured payment files that could be uploaded in bulk. 

At the center of this solution is a controlled, semi-automated workflow built using Google Sheets and XML file generation. 

In simple terms: 

prepare once, validate once, upload once. 

How the New Process Works 

The redesigned workflow breaks down into a few clear stages: 

1. IC File Preparation: The General Ledger (GL) team completes the IC payment file, this remains the trigger for the process. 

2. Structured Input via Regional Sheets: The AP team works within dedicated regional sheets to manage volume cleanly and avoid overlap. 

3. Script-Driven Data Population: Using built-in scripts, key data like amounts, beneficiaries, remittance details automatically pulled into the sheet. 

4. Controlled Manual Inputs: Only a small set of fields require manual input (execution date, currency, urgency, etc.). Everything else is standardized. 

5. Automated Mapping: Static data such as account numbers, bank details, and BICs are auto-filled through locked mappings. 

6. Review and XML Generation: After validation, the file is converted into an XML format directly from the sheet. 

7. Bulk Upload to Cobase: The XML file is uploaded in one step, completing the payment setup process.

The Impact 

The difference was immediate and measurable: 

Manual processing time (AP): reduced from ~4–4.5 hours to ~1.5 hours 

Time savings: ~65% per IC cycle 

Error risk: significantly reduced through standardized mappings and validation 

Scalability: large volumes handled with minimal additional effort 

What used to take hours of repetitive input is now handled in a fraction of the time with more consistency and control. 

Building in Control: Security & Risk Mitigation 

Automation only works if it’s trusted. From the start, we designed the process with control in mind: 

• Locked master data: Critical bank and account mappings are protected from unauthorized edits 
• Audit trails: Separate logs track both transaction-level and file-level activity, including timestamps and user actions 
• Validation checks: Built-in controls flag duplicates and enforce data integrity before file generation 
• Controlled access: Editing rights are restricted to approved users only 

The goal wasn’t just speed—it was safe, traceable efficiency.

A Practical Step Toward Full Automation 

This isn’t the final state. It’s a bridge. 

Moving to XML-based uploads creates a structured foundation for future automation, particularly the transition toward fully automated IC EFT payments within NetSuite. 

By solving today’s bottleneck, the process is now better positioned for tomorrow’s scale. 

A Small Shift with a Big Effect 

Finance teams often carry processes like this functional, but heavier than they need to be. They don’t fail loudly, so they rarely get prioritized. 

But when you look closely, the opportunity is usually there: 

Not for a full transformation. 

Just for a better way of doing the same thing. 

That’s where the real gains tend to be.