How do I track revenue using Sage Intacct project data in Loopfour?

Loopfour's Sage Intacct integration only reaches the Project object — budget, dates, customer — not Sage Intacct's separate Contracts and Revenue Management module, which is where ASC 606 revenue recognition schedules actually live. Project data can approximate revenue for reporting, but it isn't a recognized-revenue figure, and it shouldn't be presented as one.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the finance integrations guide.

What Loopfour's integration reaches	Project object only — BUDGETAMOUNT, BEGINDATE, ENDDATE, CUSTOMERID
What it doesn't reach	Sage Intacct's CONTRACT and REVRECSCHEDULE objects (Contracts and Revenue Management module)
Where real ASC 606 schedules live	Contract revenue templates and revenue recognition schedules, a module separate from Projects
What Project data is good for	A budget/ceiling proxy, timeline, and customer link — not a GAAP-compliant recognized-revenue number

Projects and Contracts are two different modules

Sage Intacct's own developer documentation describes Contracts and Revenue Management as a distinct module built specifically to address ASC 606 — the contract object carries price-list and term data, and generates revenue recognition schedules through dedicated schedule and schedule-entry objects. Sage Intacct's Project object, by contrast, sits in project management functionality: it tracks a budget amount, a start and end date, and a linked customer, with no revenue-template or recognition-schedule fields at all. These aren't two views of the same data — they're two different parts of the product, and Loopfour's Sage Intacct integration currently only implements Project Actions (getProject, createProject, listProjects), not the Contracts module.

What Project data can honestly stand in for

A project's BUDGETAMOUNT, paired with its begin and end dates, gives a coarse timeline and a spending ceiling for work tied to a customer. That's useful as a planning or forecasting input, and it's genuinely available through the integration today. What it is not: a schedule that recognizes a specific dollar amount in a specific period the way ASC 606 requires, accounting for performance obligations, modifications, or percent-complete recognition. Presenting a project's budget as "revenue recognized this period" would be wrong in exactly the way that matters to an auditor.

How to use it without overstating what it is

Pull project data (getProject or listProjects) for planning-level reporting — budget-to-actual tracking, timeline visibility, customer-level rollups — and label it clearly as budget or forecast, not recognized revenue. For anything that has to tie to the books under ASC 606, that still has to come from Sage Intacct's Contracts and Revenue Management module directly (through Sage Intacct's own UI, a report, or a future integration action), not be approximated from Project fields.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Field mapping

Project fields vs. what a real ASC 606 schedule requires

Question	Project object (reachable)	Contract / RevRecSchedule (not reachable)
Total contract value	BUDGETAMOUNT (a budget ceiling, not a contract price)	Price list / fair value price list on the CONTRACT object
Recognition method	Not present	RECMETHOD on the schedule (straight-line, percent-complete, milestone)
Amount recognized this period	Not present	Individual entries on a REVRECSCHEDULEENTRY

Frequently Asked Questions

No — Sage Intacct's own API documentation shows Project carrying budget, dates, and customer/manager links, with no revenue-template or recognition-schedule fields. Those live only on the separate Contracts and Revenue Management module.

Technically yes — Sage Intacct's API exposes CONTRACT, revenue templates, and REVRECSCHEDULE objects for this. Loopfour's integration doesn't implement them today; this page describes the current gap, not a permanent limitation.

No — Rillet's Loopfour integration reaches a purpose-built contract/usage API directly. This page is about a gap on the Sage Intacct side specifically: the underlying module exists in Sage Intacct's product, Loopfour's integration just doesn't reach it yet.

Sources

Topic

Revenue Recognition

Revenue recognition determines when — not just how much — revenue hits the books. Under ASC 606 (US GAAP) and its international counterpart IFRS 15, revenue is recorded as a company satisfies its perf…

Topic

Integrations

Every finance automation vendor publishes an integrations page: a grid of logos, a claim of "seamless" connectivity, and not much else. That page answers a marketing question — does this vendor touch…

How-to

How do I sync a Rillet contract amendment into my revenue recognition schedule?

Call Rillet's amend-a-contract endpoint with an amendment_date, an amendment_reason, and the changed items, choosing whether each item takes effect as of the amendment date or at the end of the current billing cycle. Rillet regenerates the affected revenue schedule and journal impact for review before anything posts.

Diagnostic

What breaks when Sage Intacct project budget is treated as recognized revenue?

A Sage Intacct project's BUDGETAMOUNT is a planning ceiling, not a recognized-revenue figure. A report that sums project budgets and calls the total "revenue recognized" will drift from the real ASC 606 numbers in Sage Intacct's Contracts module — budgets don't move with recognition method, performance obligations, or modifications, and nothing keeps the two in sync automatically.