Why Do Funds Need an Expense Allocation System If They Use Ramp or SAP Concur?

TL;DR. Ramp and SAP Concur code a fixed split at entry, and that part is solved. Funds still need an expense allocation system for the splits that change. The basis moves each quarter, one bill covers several quarters, and some costs wait for quarter-end figures. Funds also need approved rules and a record of each split's basis.

A partner at a credit fund told us recently that the firm uses SAP Concur and should be set. Another prospect asked what an allocation system does that Ramp does not. The answer starts with what the AP and expense tools already do well.

What do Ramp and SAP Concur already do for allocation?

They split a cost at the moment someone enters it, and they do that well.

Ramp's page on line item splits and allocation templates describes how teams "create and save reusable split configurations, ensuring consistency and saving time." Its page on split expense automations goes further. A rule can match a condition, and "Ramp will automatically apply this split for future transactions that meet the condition."

SAP Concur covers the same ground. Its course on allocating a request says: "Users can split items by percentage or monetary amount." Users can also save favorite allocations. An SAP Concur post on its invoice product says the system can "import distributions from Excel, edit the distribution, or save user-specific favorite distributions."

A senior associate on the management company finance team at one investment firm described the result. The team saves its splits in Ramp, and when a saved split fits a bill, "it just runs it for us."

A fixed split that is known when the bill arrives needs no other system. If your co-invest split is 60/40 and stays 60/40, the AP or expense tool codes it correctly every time. The gaps start after entry, where fund expense allocation begins.

Fund expense allocation is the work of dividing a shared cost across the fund entities, SPVs, and management company it served, applying the methodology each vehicle's governing documents support, producing the resulting journal entries, and recording the basis for each split in a form an auditor or examiner can sample.

Our guide on how corporate expense platforms and fund software compare covers the products one by one.

Why does a saved split go stale every quarter?

A saved split is a fixed percentage. Some shared fund costs follow a basis that moves. Software and data subscriptions split on fee-earning AUM are one example. That figure changes when a fund steps down after its investment period, and again when a new fund holds a close.

Ramp's own split automations page lists a common mistake: "Forgetting to update split rules when team structures change." For a fund that splits costs on fee-earning AUM, the basis can change every quarter.

The same investment firm runs its subscriptions outside Ramp for this reason. The senior associate explained:

"we have yearly subscriptions that is split between multiple funds, and they're driven by fee earning AUM, which changes on a quarterly basis. So that process is still manual, done on a Excel file."

The team allocates 10 to 20 subscriptions each quarter. A finance manager on the same team keeps an inputs tab with each fund's fee-earning AUM. A second tab lists every subscription and its funds. The file works. The manager said the hard part is the roll-forward: "It's essentially just copy/paste and changing a cell reference." Our guide to allocation bases covers the methods themselves.

How do you split one bill that covers five quarters?

You split it by day first, then by each quarter's basis. A subscription bill pays for a service period, and that period need not match the quarters. Each day of service belongs to the quarter it falls in. Each quarter's share then follows that quarter's basis.

The finance manager at the same firm wants the allocation exact, "really to the penny and to the day." The vendors' allocation pages describe percentages and amounts. Ramp's splitting page says: "Amounts must add up to the transaction or reimbursement total." None of the pages we read mention a service period.

Here is a hypothetical case. A market data subscription costs $96,000 for a service period of February 20, 2026 to February 19, 2027. That is 365 days across five calendar quarters. Where the fund documents allow the funds to bear it, three funds share it on fee-earning AUM. Fund III steps down in the third quarter. Fund V holds its first close in the same quarter.

The formula has two steps:

1. Quarter slice = bill amount × service days inside the quarter ÷ total service days.
2. Fund share = quarter slice × the fund's basis at quarter-end ÷ the total basis of the funds that share the cost.

For the third quarter, the slice is $96,000 × 92 ÷ 365 = $24,197.26.

Amounts are rounded to the dollar, and the total row adds the rounded rows.

The saved split charges Fund III's investors $12,530 more than the day-and-basis method. It charges Fund IV's investors $7,201 more. Fund V uses the data for three of the five quarters and pays nothing. Both methods total $96,000, so no arithmetic check flags the difference.

Why do funds park costs in an unallocated account?

The basis figures for a quarter are not final when the bill lands. So some teams book the cost first and split it at quarter-end.

The investment firm above books its subscriptions to an unallocated GL account and reclasses each fund's portion every quarter. Late bills make it harder. The senior associate said:

"sometimes you will get the bill at a later time, so you're also allocating over two quarters, so you're making sure using the fee earning AUM for each quarter accordingly for those allocations."

That is why the team keeps prior quarters' basis figures. In the example above, suppose the third-quarter slice arrives late and someone splits it on the fourth-quarter basis. Fund V then carries $2,348 more than its third-quarter share, and Funds III and IV carry less.

A second firm, an exempt reporting adviser, uses a catch-all code. The finance team codes what it can at entry. In its words, "where we can't, we put it into a code called chargebacks other." A senior accountant clears that code at quarter-end and applies the basis each item needs. The senior accountant said the workbook takes a couple of hours a quarter. The time goes into chasing whether each item belongs in the allocation at all.

The pages we read do not mention a split that waits for a later period.

Is approving a bill the same as approving an allocation?

No. A bill approval answers whether to pay. The fund question is whether this fund may bear this share, on this basis, under its LPA.

In Ramp and SAP Concur, the split sits on the document under approval. Ramp's bill pay page says approvers can "allocate costs across accounting fields before approving a bill." SAP Concur's course says "the allocations could be used to determine what managers must approve the request." A Ramp rule applies a fixed percentage that an admin or AP user saved. The pages we read do not mention a rule with a version history that someone approves once, or a basis that updates each period.

The exempt reporting adviser above described the fund side plainly. We asked whether anyone approves the split itself, beyond the approval to pay the vendor. The person who reviews that work at quarter-end said:

"there's no formal process. So [the senior accountant] will, um, do the working behind it, and I'll review at quarter end, but nothing, um, no, like, button that's clicked to sign off or anything."

Their auditors ask for the chargeback files and test them. The SEC's fiscal 2027 exam priorities say examiners will look at "the accuracy of fee and expense calculations at both the fund and investment levels." Our post on what SEC examiners ask about expense allocation covers the findings.

How do two bills for the same deal end up split two different ways?

Each person who codes a document makes a judgment. Without one rule that every matching cost follows, two legal bills for the same deal can get two different splits. Both totals still tie.

Someone on the finance team at a large investment firm named this as the main risk: "I think consistency is probably the biggest risk." The same person said: "It's hard when you have so many hands in the pie." That firm documents any change to an allocation method and takes it to its chief compliance officer before the change happens.

The SEC staff reported inaccurate allocations in exams. Its 2020 risk alert on private fund advisers says: "The staff observed private fund advisers that have inaccurately allocated fees and expenses." The alert names shared expenses allocated "in a manner that was inconsistent with disclosures to investors or policies and procedures." Our research on gaps in the allocation audit trail shows where that record breaks. Legal bills are one place where this happens, and our guide to splitting legal invoices across fund entities works through one.

Where does the data a split needs live?

It lives in the fund records, not in the AP or expense tool. A split needs each fund's commitments, invested capital or fee-earning AUM for the quarter. It needs to know which deal belongs to which fund, and what each LPA permits. At the investment firm above, the fund team supplies the fee-earning AUM each quarter from its own files.

Ramp's bill pay page answers the entity question in its FAQ. To "Is splitting across entities supported?" it answers: "Not at this time. Currently splits are supported for line item level accounting fields." So the split in the tool lands as accounting codes inside one set of books. At the firm above, those codes sit in the management company's books, with a receivable from each fund. Tracking those due to and due from balances is its own job.

Of the 80 fund finance teams we spoke with in 2026, 92% run allocations across disconnected systems. At the subscription-file firm and the exempt reporting adviser, the AP tool and the basis figures sit in separate systems.

The subscription-file firm makes a fair defense of the spreadsheet. Its controller said: "our process is a little bit open to a manual fat finger, but it's still pretty damn good." The controller looked at dedicated systems before and found them more work to maintain than the file. The cost of the spreadsheet is the quarterly roll-forward and the missing approval record, not the arithmetic. Our post on where the QuickBooks workaround breaks for funds covers the ledger side. The allocation layer sits between the AP and expense tools and the GL.

What should an expense allocation system add on top of Ramp or SAP Concur?

Check for these seven things:

1. It reads bills and card transactions from the AP and expense tools and does not replace them.
2. It stores each period's basis figures and keeps prior periods.
3. It splits a service period across the quarters it covers.
4. It holds costs until the period's basis figures exist.
5. It applies rules that a person approved once, with a version history.
6. It keeps a record for each split: the source document, the basis numbers used, the approver and the journal entries.
7. It tracks what each fund owes the management company.

Our guide on how PE firms automate quarterly expense allocation shows how teams set this up.

Where does Ceviche fit?

Ceviche connects directly to Ramp, Bill.com, Brex, Expensify, and SAP Concur, and your AP and expense tools stay where they are. AI reads each bill and drafts the line items, and every split comes from a rule a person approved or an allocation a person made. Ceviche keeps each quarter's basis numbers, so every split carries the figures it used, and journal entries post to NetSuite or QuickBooks Online. It is not a fund administrator, a general ledger or a managed service, and it does not do the allocations for you.

Frequently asked questions

What can a dedicated allocation system do that Ramp cannot? Ramp codes a fixed percentage at entry and can apply it by rule. An allocation system works after entry. It updates the basis each quarter, splits a service period across quarters, and holds costs until quarter-end figures exist. It also keeps an approved, versioned rule and a record for every split. Ramp's pages that we read do not mention a basis that updates by period or a service period.

We use SAP Concur. Is that enough for fund expense allocation? SAP Concur allocates by percentage or monetary amount, saves favorite allocations, and imports distributions from Excel for complex bills. That covers the split at entry. The fund work after entry remains. That work is each quarter's basis, costs that wait for quarter-end figures, rules for each LPA, and the record an auditor samples.

Can saved splits handle allocations that change every quarter? A saved split holds one fixed percentage until someone edits it. If the basis is fee-earning AUM or commitments, the percentage changes when a fund steps down or holds a close. Someone then updates every saved split by hand each quarter. Ramp's own page lists forgetting to update split rules as a common mistake.

How do you allocate an annual subscription that spans several quarters? Divide the bill by its total service days. Multiply by the days that fall inside each quarter to get that quarter's slice. Then split each slice on that quarter's basis. In the example above, a $96,000 subscription gives a third-quarter slice of $24,197.26, which three funds share on third-quarter fee-earning AUM.

Is a well-built allocation spreadsheet good enough? It can be, for a stable set of entities and a few recurring costs. One controller called the firm's file "still pretty damn good." The costs are the quarterly roll-forward, a typo that carries through every downstream figure, and no record of who approved each split. Those costs grow with each new fund and each new subscription.