Implementation and migration
Receivables, payables and timesheets sync both ways on a fifteen-minute cycle. Every rule that could round, merge or classify a dollar is written down and refuses to guess.
01Key numbers
02The situation
Invoices, bills and timesheets were rekeyed between Salesforce and the accounting system by hand. The same seven-line invoice existed twice, and the two copies drifted.
The chart of accounts reuses six leaf names across regions, so any lookup by name matched three rows at once and filed every region’s revenue under one of them.
Recognise this in your own org?
03What we built
Tokens live outside Salesforce. The in-org button only queues work, and a hosted runner executes it.
Two enforcement layers trim precision as data leaves for the accounting system. No Salesforce field was narrowed, because the platform data is not wrong. The single exclusion is the exchange rate, and the reason is stated: it is not an amount, and trimming it would move a $5,000 bill by about 21 cents.
Lines merge only when location, product, description, unit price, discount, tax rate and class all match, because the company reuses one product code for customer-specific configurations. A combined line is emitted only when it still balances. Either way the invoice is worth precisely what it was worth.
Resolution matches the fully qualified account name first and accepts a bare leaf only when it is unique. Otherwise it throws. A wrong region on a revenue line is worse than a failed sync, because a failed sync is visible.
3,169 bills carry purchase-order style document numbers keyed by hand. A reconciliation sweep found 34 completed purchase orders missing from the accounting system and linked 30 that had already been keyed manually, stamping a drift note wherever totals differed by more than two cents.
We will demonstrate any of these live, on the real org,.
On 23 July 2026 the scheduled job stopped for about twelve hours. It loaded, exited with code zero, and raised no error, so roughly fifty cycles were missed while accounting queued invoices and watched nothing happen. It now runs on hosted infrastructure with a heartbeat object and an hourly watchdog. If it stops again you get told, not the controller.
04Outcome
Both directions have been live since 21 July 2026, with the parts that could get a number wrong deliberately held back.
Precision handling was validated by replaying 135 live synced invoice lines rather than by writing new test cases.
Keep reading
Sixteen archive objects populated with zero failures, and two phantom invoices caught and removed before they touched a live record.
One question drove the whole design: where is the inventory value now. The answer required a state machine, an audit trail on every movement, and an honest note about two parallel ledgers.
Tell us what is broken. You get a written read on it within one business day, before any money changes hands.