Help centre · Projects
P&L Reconciliation
Open this screen in Saral/projects/reports/reconciliation
Proves that the project reports capture all of the group's P&L: for each company, its P&L activity (sales and costs, excluding depreciation) split into what is tagged to a project and what is not, with the untagged amount by account so it can be tagged in Xero. A finance desk runs it before a month-end or year-end pack; it is the answer to 'can I trust the project totals'.
You enter
- The window — the last twelve months by default, a run of months on the slicer, or one financial year from the chips (carried in the URL).
Saral fills in
- Each company's P&L activity from the journal lines, excluding depreciation, split into lines that carry a project tag and lines that do not, with coverage as a percentage — a dash, never 100 %, where there is no activity to measure.
- The group totals: coverage, the untagged amount, how many companies have a gap, and the depreciation left out by design.
- The untagged lines by account and company — sales, cost, total and line count — biggest first.
- The financial-year chips from the group's configured year end.
It produces
- The reconciliation as a PDF or an Excel workbook with live formulas, previewed first.
- The list of accounts to tag in Xero to close the gap.
What this page is for
Every project report in the module is built from the ledger lines that carry a project code. A line without one — a wage run posted to no job, a supplier bill coded to overhead by mistake, a sale with the tracking left blank — is invisible to all of them, and the project totals are quietly short. This page measures that shortfall and names the accounts it sits in.
Company basis, on purpose
Every company's books are counted as they stand, and an intercompany sale counts in full on both sides. That is deliberate: the question is whether each line carries a project code, not whose cost it ultimately is, so eliminating pairs here would hide untagged lines. The figures will therefore not tie to a group-basis report, and the header says so. Depreciation is left out because it is never project-attributable.
Closing a gap
The untagged table is the work list: the account, the company, how much and how many lines. Open the account in Xero, put the project on each line, and the next sync moves it into the report. A company at a dash has nothing to reconcile in the window; a company in red has lines the project reports cannot see.
What a good result looks like
Coverage at or near 100 % for every company with activity, and an untagged table that is empty or holds only lines nobody would ever put on a job. A figure of 100 % with no activity is never shown — that would be a claim about data that is not there.
Who sees it
The page needs the Projects settings permission — a finance desk. The first load after a quiet spell rebuilds from the journal and can take up to half a minute; a later window change keeps the previous figures on screen, dimmed, until the new ones land.
Where next
Company Recharge Coverage asks the neighbouring question — whether each company's whole cost is recharged or declared; Explore and the CVR read the lines this page has just proved complete.
Next screen: /projects/reports/recharge-coverage
Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.