A green integration dashboard can mean that recent requests succeeded, not that every required business record arrived correctly. Reconciliation compares what should exist with what actually exists. It is particularly useful when staff rely on a connected system to make operational decisions.
Related service: Custom software development- 01Define the source, scope and cutoff.
- 02Match records by agreed identifiers.
- 03Classify differences and acceptable delay.
- 04Assign an owner and repair action.
- 05Compare again and retain the outcome.
SECTION 01
Define what agreement between systems means
Start with the important business relationship: an approved order should have a corresponding fulfillment record, for example. Identify which source states qualify, how cancelled items behave and how much processing delay is normal. Comparing all records indiscriminately can produce noise that teaches staff to ignore the report.
Webhook delivery guidance from GitHub includes recovery of missed deliveries, while OWASP logging guidance supports useful event context and traceability. A reconciliation report adds a business-level check beyond those delivery records. Its proposed rules should be reviewed by the data owner: a technical success response cannot decide whether an order's status or quantity is commercially correct.
SECTION 02
Illustrative example: orders and warehouse instructions
Suppose the sales system shows 120 approved orders for a daily cutoff, while the warehouse system shows 119 matching instructions. Equal totals would not be sufficient either: one duplicate could conceal a missing order. The report should identify the unmatched source order and detect any repeated destination reference.
In this hypothetical example, another order exists in both systems but has a different delivery address. The sales system owns the address until warehouse release; after release, changes require review. The report therefore proposes investigation, not an automatic overwrite. A pending item within the agreed delay is listed separately from an overdue exception that needs action.
SECTION 03
Keep repair accountable and repeatable
A first release may reconcile one important object and a handful of fields once daily. This is often more useful than a large dashboard covering every event. Existing platform exports can support an initial comparison when volume is modest, provided identifiers and cutoff definitions are reliable. Automate only after the business has agreed how differences should be resolved.
Test a missing record, duplicate reference, changed field, late arrival and intentionally excluded state. Verify that the comparison records its cutoff and does not treat ongoing writes as unexplained corruption. Repairs should preserve the original evidence, identify the operator and be safe to repeat. Re-run the comparison after repair; marking an exception resolved without checking the destination turns the report into a checklist without proof.
SECTION 04
Frequently asked questions
Is reconciliation the same as integration monitoring?
No. Monitoring tracks execution and failures. Reconciliation checks whether the resulting business records agree according to defined ownership and timing rules.
Should every mismatch repair itself automatically?
No. Some differences are expected or require a business decision. Automate only unambiguous repairs and keep the evidence and result visible.
How often should the comparison run?
Choose a frequency based on operational impact, data volume and normal integration delay. A daily control can be sufficient for one workflow and too slow for another.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Webhook delivery practicesGitHub Docs
- Application logging guidanceOWASP Foundation
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy