Before you start
- Provide source sheets, a target template and rules for customer, channel and project dimensions.
- Confirm column mappings, source priority, accounting periods and formulas. Use import/export files when the ERP has no API.
Reconciliation and P&L analysis: from cross-checking sheets and asking around about definitions to one recomputable line
Fiitx can consolidate Excel sheets or ERP exports using your accounting definitions, produce a summary matching your target template, and report source conflicts and missing metrics. Amounts aggregate by rule and ratios are recalculated. Without an ERP API, use import/export files reviewed by a person before write-back.
Requirements and verifiable outputs
What you receive
- A summary matching the target column names and order, plus source conflicts and missing metrics.
- Amounts aggregate by the agreed rules; ratios are recalculated from aggregate numerators and denominators. Inputs and outputs can be retained for review.
Scope and limits
- Conflicts require review. A value selected by source priority is not a confirmed accounting fact.
- The example neither connects to an ERP nor writes back. Missing net profit is not estimated.
Public verification example
Synthetic fixtures processed by Fiitx's existing calculation modules. These are not client records, delivery footage or measured time savings; only the rules listed below are verified.
Example verified:
| Customer | Revenue | Gross profit | Gross margin | Net profit |
|---|---|---|---|---|
| DEMO-B | 9000 | 900 | 10% | Missing |
| DEMO-A | 1000 | 500 | 50% | Missing |
| Total | 10000 | 1400 | 14% | Missing |
What to check
- Source A's subtotal is excluded. Revenue of 10,000 and gross profit of 1,400 produce a 14% margin, rather than the 30% average of the two row margins.
- DEMO-A has gross profit of 500 in one source and 600 in another. The difference of 100 is reported separately; missing net profit remains empty.
01
Where it used to get stuck
The definitions live in people, not in documents
Which channel a client belongs to, which month a rebate is spread across — these judgements are rarely written down. When the person who held them leaves, a discontinuity appears, and it usually surfaces a quarter later.
Columns stop matching, and the failure is silent
Exports arrive with stray spaces in headers, a word changed, the order shuffled. Reading by position does not error on any of that; it produces a plausible wrong number.
The ERP has no open API
Many finance systems only offer import and export templates. That segment stays manual, and the whole line breaks in two at that point.
02
How it runs once handed over
Join several source sheets across your own dimensions
Client, channel, project and company follow your existing attribution rules, held as configuration rather than hardcoded in a script.
Match columns by name, tolerant of whitespace and small renames
When a match genuinely fails it stops and asks rather than skipping the column and carrying on. This rule exists because the alternative was learned the hard way: skip a column silently and the report still looks tidy, while the wrong number surfaces months later.
Definitions delivered per organization — change once, everyone gets it
How rebates spread, which accounts roll into which metric, how periods are cut: all of it lives in a definitions profile in the cloud, not in one person's workbook.
Systems without an API are reached through their import templates
Where the ERP offers no API, files are generated against its own import template and a person approves them before they go in. A human still gatekeeps — they just stop filling rows by hand.
Results kept as snapshots you can recompute
Every run stores its inputs, the version of the definitions used, and the output. Any period can be recomputed later and compared.
03
Where it stops for a person
- An unmatched column or a gap beyond the threshold stops the run and asks — never a silent skip
- Any file destined for the ERP waits for a person to approve it
- Definition changes are versioned: what changed, who changed it, and from which period it applies
How it is accepted
- Take a period already produced by hand and reconcile it cell by cell
- Recompute another period: the same inputs must produce the same result
- Add a stray space and rename a source column on purpose — it should raise an anomaly, not produce a number
04
Where the definitions come from
06
Questions
Our ERP has no API. Can this still be automated?
Yes. Where there is no interface, its own import and export templates are used: exports for reading, generated import files for writing, approved by a person first. That is not a workaround — it removes the most mechanical part of the manual work.
Our definitions change often. Does that mean a code change every time?
No. Definitions are configuration, maintained per organization in the cloud, and apply from the next run. Changes are versioned so you can see which period they started from.
Can results be recomputed? Audit wants to see the process.
Every run stores inputs, the definition version and the output, so any period can be re-run and compared.