Chrys Capital Invoice Processor

The Problem

Private equity back offices process vendor invoices that must be split across multiple legal entities — fund vehicles, GPs, and co-investment SPVs — based on allocation tables buried inside signed letters of proposal. A single Acme Corp retainer for "Project Denim" can fan out into three invoices billed to ChrysCapital X LLC, ChrysCapital Fund X, and Two Infinity Partners at fixed percentage shares, and the AP clerk is expected to verify each invoice against the engagement letter before release.

The manual check takes 15–25 minutes per invoice and breaks down at scale. Vendor names drift between "Acme Corp Pvt. Ltd." on the invoice and "Acme Corp Private Limited" in the proposal. Project references arrive as "Project- Denim" against a contract that simply says "Denim". Entity names carry stray commas — "ChrysCapital X, LLC" versus "ChrysCapital X LLC" — that defeat any exact-string match in the ERP.

The failure mode that matters is silent: an invoice gets paid against a fund vehicle that was never party to the engagement letter, and the misallocation surfaces six months later during the LP audit when the management fee waterfall does not tie. Recovering that payment from the vendor or rebooking it across funds is materially harder than catching it at intake.

Why It Matters: Context

Under Section 16(2) of the CGST Act, input tax credit on a vendor invoice is only available to the registered entity named on the tax invoice as the recipient. For a fund manager running 8–15 investment vehicles, billing the wrong entity does not just create an internal allocation problem — it creates an ITC eligibility question and an audit trail that contradicts the signed engagement letter held in the legal file.

Mid-market PE and VC firms typically run this control on a spreadsheet. The CFO's office has 3–4 finance staff covering 50–200 active vendor invoices a quarter across professional services, due diligence, and portfolio support engagements. There is no dedicated procurement system, no contract repository tied to the AP module, and no four-eyes check beyond a partner countersignature on payments above a threshold.

When the control fails, the consequence is concrete: an invoice charged to a fund not listed in the allocation table either gets reimbursed by the GP at its own cost, or it sits as a reconciling item in the fund's capital account statement and shows up as an LP query letter.

What This Workflow Automates

1. Classifies each uploaded PDF as either an Invoice or a Letter of Proposal using document signals — title, presence of an invoice number such as INVGGN252600455, HSN/SAC code for management consulting services, or the entity allocation table with percentage shares.
2. Extracts structured fields from the invoice: vendor name, invoice number, invoice date, bill-to entity, project reference, professional fees, fixed expenses, IGST, total, and currency.
3. Extracts the engagement scope from the letter of proposal: vendor name, project name, total fee, payment milestones (typically 50% on confirmation, 50% on completion), currency, and the full entity_allocations array with each entity name and percentage share.
4. Runs vendor name reconciliation at an 85% fuzzy threshold, normalizing "Pvt. Ltd." to "Private Limited" and "Ltd." to "Limited" before comparison so that legal-form abbreviations do not produce false mismatches.
5. Runs project reference reconciliation at a 75% threshold after stripping any "Project-" or "Project " prefix from the invoice side, returning NO_MATCH rather than a silent pass when the field is absent on either document.
6. Runs entity allocation reconciliation by scanning every row of the proposal's entity_allocations array against the invoice bill_to_entity at an 80% threshold, treating "ChrysCapital X, LLC" and "ChrysCapital X LLC" as the same legal entity.
7. Runs a currency check that returns MISMATCHED when an INR invoice with IGST is presented against a USD-denominated proposal for an offshore fund, and routes the document to treasury review before FX conversion.

All of this happens in roughly 18 seconds per invoice with deterministic outputs every controller can audit.

Edge Cases We Simulate

The workflow ships with a battery of synthetic test scenarios that exercise every failure mode we have seen in real-world data. Each scenario produces a deterministic outcome that an auditor or controller can verify in seconds.

Sample Documents

Download or inspect the seeded sample files used to demonstrate this workflow:

Sample Results

On a representative quarterly batch of 120 ChrysCapital professional services invoices, the workflow processes the full set in under 40 minutes against a manual baseline of 30–35 hours. Each invoice produces a four-line reconciliation report — vendor, project, entity allocation, currency — with an explicit MATCHED, MISMATCHED, or NO_MATCH verdict and the underlying field values from both documents shown side by side.

The exception class that consistently justifies the control is the bill-to-entity miss: an invoice raised on Two Infinity Partners against a proposal whose allocation table only lists ChrysCapital X LLC and ChrysCapital Fund X. The workflow blocks the payment at intake, flags that the engagement letter does not authorize billing to that fund, and forces either a contract amendment or a corrected invoice from the vendor before the payment run.

Why Automation Wins Here

The workflow compresses a 20-minute manual three-way check into an 18-second deterministic run and eliminates the silent-pass failure mode where a comma or a "Pvt. Ltd." abbreviation causes a real match to be filed as an exception. Across a quarterly volume of 120 invoices, the time saving is approximately 30 hours and the four exception classes — vendor drift, project prefix, entity suffix, currency — are caught before the payment file leaves AP.

Each invoice's reconciliation output — the extracted fields from both documents, the four rule verdicts, the threshold values used, and the matched entity allocation row — drops into the controller's audit file as a single artifact, ready for the statutory auditor's vouching sample and for the LP-side fund administrator review.

Frequently Asked Questions