Accounting integration patterns: invoices, classes and the four-decimal boundary

Rounding belongs at the accounting boundary, not in the source. A replay of live invoice lines is the evidence, not an assumption.

1. VideoRounding at the boundary, and why no Salesforce field was narrowedPreview9 min
2. Video21 of 135 replayed invoice lines: 16% with more than four decimal placesDivision and floating-point noise, found by replaying real synced lines rather than assuming the input was clean.8 min
3. VideoTwo enforcement layers, so one missed cap does not reach the ledger6 min
4. VideoThe single exclusion: an exchange rate is not an amount6 min
5. ReadingReading: what trimming the exchange rate would have moved on a real bill5 min
6. ReadingReading: a rounding boundary in one function, not scattered5 min
7. LabLab: cap a unit price at the boundary without touching the source field13 min

Combine only when every attribute matches, and only emit a combined line when it still balances. Nothing is invented.

1. VideoConsolidating lines only when every attribute matches8 min
2. VideoLocation, product, description, unit price, discount, tax rate and class, all seven7 min
3. VideoThe invariant: a combined line is only emitted when it still balances7 min
4. ReadingReading: why one product code covers many customer-specific configurations5 min
5. ReadingReading: dedup within a $1 and 7 day window, and why that width5 min
6. LabLab: consolidate a real invoice and prove the total did not move13 min

Six leaf names reused across regions, and the rule that stops a bare lookup from filing one region’s revenue under another.

1. VideoA bare name lookup that matched three rows and filed one region under another8 min
2. VideoFully qualified name first, a bare leaf only when it is unique7 min
3. VideoThrowing rather than guessing when a leaf name is ambiguous6 min
4. VideoSix leaf names covering 5,905 of 5,945 classed lines6 min
5. ReadingReading: reading a chart of accounts before you resolve against it5 min
6. LabLab: resolve a class by fully qualified name, then by a forced ambiguity13 min

PO-style document numbers keyed by hand, a sweep that finds what is missing, and drift notes instead of silent overwrites.

1. Video3,169 bills carrying PO-style document numbers keyed by hand8 min
2. VideoA sweep that found 34 completed purchase orders missing from the ledger7 min
3. VideoLinking 30 already keyed manually, instead of inserting duplicates6 min
4. VideoStamping a drift note when totals differ by more than two cents6 min
5. ReadingReading: PO-style numbers, and why hand-keyed drift happens5 min
6. LabLab: write a reconciliation sweep that links before it inserts13 min

The in-org button only queues. A runner outside Salesforce does the work, so a third-party outage can never block a save.

1. VideoSplitting the queue from the runner, so a third party can never block a save8 min
2. VideoA 15-minute cron for the batch path, and an on-demand path beside it7 min
3. VideoA real seven-line invoice, round-tripped in 14 to 18 seconds6 min
4. ReadingReading: where the token lives, and why it is not in Salesforce5 min
5. LabLab: design the queue record and the runner contract between them13 min

A classification measured at 95.1% accurate, and a feature that stayed off because the controller had not signed off yet.

1. VideoAuto-creating customers and projects, built and deliberately left offPending the controller’s sign-off, with a read-only preview command that generates her verification package.8 min
2. VideoA read-only preview command, so the feature can be judged before it runs7 min
3. VideoClassification measured at 95.1% accurate on a 140-order corpus6 min
4. ReadingReading: shipping a switch instead of a decision5 min
5. ReadingReading: what 95.1% accurate means, and what it excludes6 min
6. LabLab: build a preview command that changes nothing13 min

A three-way reconciliation across the CRM, the retiring system and the ledger, with the residue itemised rather than hidden.

1. VideoReconciling three systems on one legacy order key8 min
2. Video97% keyed, with the residue itemised for the controller7 min
3. VideoPer-order reconciliation, and what "agree or explained" actually means6 min
4. ReadingReading: presenting an unreconciled residue without hiding it5 min
5. LabLab: build a three-way reconciliation report with an itemised residue13 min

Bringing rounding, consolidation, class resolution and reconciliation together into one integration a controller can trust.

1. VideoA pre-ship checklist for money that has to be exactly right7 min
2. VideoTesting an accounting sync without touching the live ledger6 min
3. ReadingReading a reconciliation report the way a controller will read it5 min
4. ReadingReading: reporting an accuracy figure with the corpus it was measured on5 min
5. LabLab: bring one invoice through the full pipeline end to end14 min
6. QuizCheck: accounting integration patterns13 min