Where transaction processing breaks across entities and currencies

This process usually breaks at the points where one team hands a transaction to another: matching payment requests to the obligation or order behind them, converting foreign currency, posting to the ledger, and agreeing balances with counterparties. Each break leaves a trace in suspense accounts, holds and manual journals.

Handoffs that lose information

The first loss happens at intake. A vendor invoice, travel claim or grant drawdown arrives without a usable reference to the order or obligation that authorised it. Someone in payables then hunts for the match by hand. The clearest sign is a holds queue that keeps growing while the same suppliers are queried again and again.

Receiving is the next weak joint. Goods arrive and the requester knows it, but nobody records acceptance in the system. The invoice fails the match and sits. Look for disputes where the buyer insists delivery happened and payables insists it did not. Both are right, and the record is simply missing.

Between subledgers and the general ledger, detail often disappears. Feeds arrive summarised, so a balance cannot be traced back to the transactions and source documents beneath it. Reconcilers who routinely ask operational teams for raw downloads are showing this gap.

Asset information suffers the same way. Purchases, leases and constructed assets get capitalised late, or coded as expense first and reclassified afterwards. When the asset register and the ledger disagree, or depreciation keeps arriving as catch-up entries, the handoff from procurement to fixed assets is not working.

Exceptions that pile up

Foreign payments carry a rate question nobody owns. The rate applied when the invoice was recorded differs from the one used at payment, and the difference lands somewhere vague. Small unexplained amounts in exchange gain and loss accounts point to it. So do suppliers reporting that funds arrived short.

Intercompany and counterparty disagreements are the larger version. One entity books a charge and the other does not, or books it in a different period or currency. The item goes to suspense and ages there. When eliminations at consolidation need a balancing plug, suspense has stopped being temporary.

Netting is skipped more often than people admit. A vendor owes money back, yet a fresh invoice from that vendor is paid in full and the credit is chased separately. Open receivables from suppliers who are also being paid regularly reveal the habit.

Payment timing creates its own exceptions. Discount deadlines and late interest depend on the date an invoice was properly received, and hold time is easy to forget. If interest appears on invoices that payables considers on time, the clock is being started in the wrong place.

Advances are another trap. Travel and grant advances should be liquidated against later claims. Staff who have filed every expense claim yet still show an open advance balance mean the offset step is being missed.

Workarounds that hide the problem

Manual journal vouchers are the most common patch. A mismatch between subledger and ledger gets fixed with an adjusting entry, approved quickly because it looks routine. The same correcting entry recurring each period is the tell. It means the fault upstream was never fixed.

Some teams warehouse payments outside the system. Items not yet due are kept in a spreadsheet and released by hand. Disbursement schedules then have to be rebuilt before anyone can certify them, and quality checks happen on the spreadsheet, not on the record of truth.

Match tolerances get overridden. Approvers clear failed validations with comments such as "per email" or "agreed with requester". Read a sample of approval notes. Vague justifications on a steady stream of overrides show that the control has become a formality.

Adjustments are sometimes recorded as new payments in place of corrections to the original. Audit then sees two payments, one apparently duplicated. Recovery letters to suppliers for overpayments that were really adjustments are evidence of this.

Questions to ask the people who run it

The documented flow and the daily practice rarely match. These questions tend to surface the difference:

• When an invoice fails the match, who actually fixes it, and how do they find the missing order or receipt?
• Which exchange rate is used for a foreign payment, and who decides when it differs from the rate on the invoice?
• What sits in suspense right now, and what is the oldest item anyone remembers clearing?
• Which journal entries get posted every period without anyone questioning them?
• Is there a spreadsheet, shared mailbox or personal tracker that the process cannot run without?
• How does the team learn that a counterparty has booked something differently?
• When a supplier owes money back, what stops the next payment going out in full?
• Who checks that advances are cleared when the final claim comes in?
• Which approvals are given without opening the attachment?
• What would break first if the person who usually reconciles intercompany balances were away?

Listen for hesitation and for answers that begin with a name. A task that depends on one person, or on a file only that person maintains, is where the next change is most likely to cause damage.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.