How to use the Data Reconciliation Tool.
Reconciliation requires a matching key and a policy for tolerances. Keep missing records separate from matched records with conflicting values.
Make the workflow fit your task.
Match records using an agreed identifier and normalize only confirmed formatting differences. Compare amounts with stated currency and tolerance rules. Report missing records, duplicate keys and value conflicts as separate groups, preserving both systems' values.
- What you provide
- Two record sets and matching rules.
- What you get
- Matched, missing and conflicting records.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
System A records invoice 12 at $100; system B records invoice 12 at $105.
Completed example
Matched identifier with a $5 amount difference. Preserve both source values and investigate the discrepancy.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should differences within a rounding tolerance disappear from the report?
Keep the tolerance and classification visible. A tolerated difference is still a difference, especially when many small amounts accumulate.
Why does reconciliation show many unmatched invoices with similar numbers?
Check prefixes, leading zeros and key types. Confirm equivalence before normalizing identifiers across systems.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑