Expense reports and Pennylane: why reconciliation is still manual
In a services company of 20 to 100 consultants, monthly expense report reconciliation represents a full day per month in the accounting team on average. Pennylane handles billing well, but it doesn't solve the upstream problem: mapping between an expense report and the project it belongs to is not a Pennylane feature. It is a layer that is missing between the input sources and the billing tool.
What this process actually costs
One day per month is 12 days per year. For an accountant with a fully-loaded cost around €50,000 annually, that is approximately €2,400 in direct cost. This figure is minor. What isn't minor is the cost of the errors this process produces.
An expense report allocated to the wrong project generates an incorrect line in the invoice draft. If the error isn't caught before invoicing, the client receives an invoice that doesn't match their own tracking data. Best case: an email exchange. Worst case: a credit note to issue, an accounting correction, and a client relationship that degrades over something that should never have existed.
What Pennylane does, and what it doesn't
Pennylane is designed to manage outgoing billing, collections and accounting for small and medium-sized structures. It does this well. Its bank connectors, payment tracking interface and lettering logic are genuine assets for a lean Finance team.
What it doesn't do is decide which project to allocate an expense report received by email as a PDF. This is not a Pennylane flaw: it is not its role. Pennylane is an accounting and billing tool, not a business process orchestrator. The NDF-to-project mapping logic requires knowing contractual rules by client, analytical codes by project, mission periods and reimbursement rules by expense category. This information doesn't live in Pennylane: it lives in the project management tool, in the CRM, and often in the account manager's head.
Why the manual process degrades over time
At the start, the mapping is manageable. The rules are known, the projects few, the exceptions rare. The person processing expense reports knows that the lunch with a particular client goes on project X and the train ticket bought last week goes on project Y.
Three years later, the project portfolio has doubled. Some clients have multiple active projects simultaneously. Consultants work part-time across two assignments. Allocation rules have evolved with the contracts. The person who had the rules in their head has changed roles. Their replacement inherited an Excel file with rules from that time, not all of which have been updated.
The process doesn't degrade linearly. It degrades exponentially, because the number of exceptions grows faster than overall volume. With 50 expense reports per month, 5 cause problems. With 200 per month, it's not 20 that cause problems: it's often 40 or 50, because project overlap cases, expenses shared between clients, and reports from transition periods multiply with portfolio complexity.
What a reconciliation agent does
A reconciliation agent for expense reports aggregates input sources, applies configured mapping rules, and pushes validated lines into Pennylane as drafts ready to be integrated into invoices.
Aggregation covers the heterogeneity of real formats: Pennylane export for expenses entered directly in the tool, Excel files for reports submitted by certain consultants, scanned PDFs for paper receipts, email attachments for reports sent directly to accounting. These four formats coexist in most services companies, and the agent handles all four.
Mapping applies rules in configured priority order: first the project code explicitly entered by the consultant, then the mission period to identify the active project on the expense date, then rules by expense category and client. Lines for which no rule produces a match with sufficient confidence are escalated for human validation with full context: consultant name, expense date, amount, category, projects active during the period.
The push to Pennylane creates drafts in the correct format, on the correct analytical codes, ready to be integrated into the month's invoices without re-entry.
What automation doesn't replace
The decision on disputed cases remains human. An expense report submitted against a project whose contract has just been suspended, a shared expense between two clients with no pre-existing allocation rule, an expense whose category doesn't match any contract line: these cases require a judgment call that only the person who knows the commercial context can make.
Automation doesn't eliminate this arbitration work. It concentrates it. Instead of spending a day processing 200 lines of which 170 are mechanical, the Finance team handles 30 cases that genuinely require a decision. Total time drops from 8 hours to 1 hour, and decision quality improves because context is presented in a structured way rather than reconstructed manually from multiple sources.
If your expense report process matches this description, a 30-minute call will check whether your configuration is automatable. Book a scoping call