Read fictional card activity and accounting configuration.
Independent systems case study · 2026
From card activity to review-ready accounting.
I built a simulated workflow for AK Labs, a fictional software company, that validates corporate-card transactions, applies accounting mappings, routes exceptions, posts balanced journals to a QuickBooks Online developer sandbox, and verifies the read-back against source activity.
- 20
- fictional source transactions
- 8
- exception records routed
- 12
- QuickBooks journals verified
- $0.00
- source-to-export difference
The business problem
Finance needs clean data—and a clear path for everything else.
Corporate-card activity can arrive with missing documentation, inconsistent accounting dimensions, duplicate records, or absent approval. Sending every row directly to accounting makes review slower and increases correction risk.
The case study separates ready records from exceptions, gives each issue an owner and next action, and reconciles eligible activity before export.
How might we turn a mixed-quality transaction file into a controlled, explainable accounting workflow?
Workflow
Configuration first. Exceptions stay visible.
Vendor-to-GL, entity, department, and approval requirements are stored as editable rules. The workflow applies those rules consistently while preserving a review trail.
Check documentation, mappings, approvals, and duplicates.
Assign each exception an owner and corrective action.
Create balanced debit and credit journal lines.
Post to QuickBooks sandbox, read entries back, and reconcile to source.
Evidence
The outputs are inspectable, not implied.
The repository includes the source data, configuration, validation logic, exception queue, journal export, QuickBooks sandbox reconciliation, operating documents, and automated tests.
Twenty fictional transactions evaluated.
Twelve transactions produced 24 balanced journal lines.
Eight records routed across documentation, mapping, approval, and duplicate controls.
Twenty-four lines read back with $6,854.06 in debits and credits and a $0.00 difference.
Validation, mapping, payload, balance, and read-back behavior tested.
Controls
Designed for explainable review.
Receipt and memo completeness
Blocks incomplete records and assigns corrective action to the cardholder.
Vendor, entity, and department mappings
Translates business rules into editable configuration rather than hard-coded decisions.
Approval threshold
Routes transactions above $1,000 without recorded approval to the manager.
Duplicate transaction IDs
Prevents repeated source records from reaching the accounting export.
Journal balance
Confirms total debits equal total credits before the output is ready for review.
Source-to-export reconciliation
Ties eligible activity to the generated journal with a documented $0.00 difference.
QuickBooks read-back
Retrieves posted sandbox journals and reconciles them to eligible source activity.