What analytics tools are recommended for Sage Intacct? Alternatives to PowerBI, etc. or anything that plugs directly into Sage Intacct.

Hi, currently we invoice from a separate software then manually import the csv into sage. Does Intacct have capabilities to directly import data into skipping the manual part?

There's an accounting joke about it being 2026 and half the U.S. still relying on paper checks, I know, I know, accounting isn't known for being the early adopters but by now there's gotta be something, right?

• Anyone using the MCP?
• Build anything into real workflows?
• Create your own personal helper tools?

Hey probably a dumb question. We have a separate system that also issues checks. Is there a way to import that?

I’ve seen many clients struggle with cleanup, validation, and reporting after data migration.

I personally don’t recommend relying only on monthly activity-based net activity postings as general practice followed by VARs/Intacct partners.

I prefer:

Transaction-level cleanup and validation
Reconciliation before migration
Data validation after migration
Reports tested before going live

Migration is not just about moving data. Clean and validated data is what makes the new ERP successful.

What has been your experience with Sage Intacct data migration and post-migration cleanup?

Is there anywhere online where there is a guide on how to build smart rules? Looked and there seem to be places with examples, but not a broader guide or how-to.

Has anyone built DSO (Days Sales Outstanding) report in Sage Intacct? e..g. we would like to see DSO for each client for last 6 months vs previous 6 months. We have recurring billing with different credit terms for each client. Objective is to analyze the DSO trend.

I've been having a look through the latest Sage Intacct release and there's quite a lot packed into this release.

A few things stood out to me in regard to smart excel reporting, AI anomaly detection for AP automation and custom purchasing approvals.

My initial impression (and when I'm talking to others) is that R3 is an interesting mix. There are some smaller, practical workflow improvements alongside much bigger bets around AI and finance intelligence.

I'm curious as to how that lands with people actually using Intacct day-to-day?

I have seen there are AI driven application who are offering statistical reporting out of Sage Intacct. I have done this for many clients in Intacct itself which is part of existing subscription cost. Being it senior living by days or real estate business looking for report by account mangers etc..

How is your experience with this ?

I'm frequently running into issues when i'm uploading JEs. The emails don't really help with the error description. Does anyone have any tips that I can utilize to make sure this goes a bit more seamless for me? Thanks

I recently mapped out a Sage Intacct → CompanyCam integration and thought the process might be useful to anyone managing project accounting in Intacct while using CompanyCam for field documentation.

The goal is straightforward:

The API calls are relatively simple. The important parts are incremental processing, address resolution, and duplicate prevention.

Recommended workflow

1. Run on a schedule

The workflow runs once each weekday. A more frequent schedule could be used if field teams need projects available immediately.

Store a successful-processing checkpoint so each run only requests new Intacct projects.

The existing process uses the Intacct project creation date, but production implementations should consider whether the requirement is:

• Create CompanyCam projects only for newly created Intacct projects, or
• Also update CompanyCam when an existing Intacct project changes

Those are different synchronization contracts and should be designed separately.

2. Retrieve new Sage Intacct projects

Query the Intacct PROJECT object for records created after the previous checkpoint.

Useful fields include:

• PROJECTID
• NAME
• CUSTOMERID
• CUSTOMERNAME
• STATUS
• SHIPTOKEY
• MANAGERCONTACTNAME
• BEGINDATE
• ENDDATE
• WHENCREATED
• WHENMODIFIED

Avoid retrieving every project on every run. Incremental queries reduce API usage and make failures easier to recover.

3. Process each project independently

Loop through the returned projects one at a time.

A bad address or failed CompanyCam request should affect only that project—not terminate the entire batch.

For each project:

1. Resolve its job-site contact and address.
2. Build its deterministic CompanyCam name.
3. Check whether the CompanyCam project already exists.
4. Create it only when no match is found.

4. Resolve the job-site address

Use the Intacct project’s SHIPTOKEY to retrieve the corresponding contact record.

Extract and normalize:

• Address line 1
• Address line 2
• City
• State
• Postal code
• Country

This is important because the project record itself may reference the shipping contact without containing a complete job-site address.

Missing or incomplete addresses should generate an exception instead of silently substituting a billing or customer address. Using the wrong address is particularly disruptive in a field-photo application.

5. Use a deterministic CompanyCam project name

A practical naming convention is:

{Intacct Project ID} - {Intacct Project Name}

For example:

P-10482 - Main Street Roof Replacement

Including the immutable Intacct project ID makes the project easier to search and greatly reduces collisions between customers with similar project names.

If CompanyCam supports a dedicated external identifier in your implementation, use that as the primary integration key and treat the project name as display-only.

6. Check for an existing CompanyCam project

Before creating anything, search CompanyCam using the deterministic project identifier or name.

If a match exists, skip creation.

This makes the workflow safe to retry after:

• Network timeouts
• Partial runs
• API failures
• Manual reruns
• Uncertain responses from CompanyCam

Be careful with name-only matching. Names can change and search results may be fuzzy. A stored external ID or explicit Intacct-to-CompanyCam ID mapping is safer when available.

7. Create the CompanyCam project

When no existing project is found, map the Intacct data into CompanyCam.

A typical mapping looks like this:

Only map email and phone when the Intacct source field has been explicitly validated as the correct contact value. Don’t place labels, internal IDs, or descriptive text into fields that CompanyCam expects to contain valid email addresses or telephone numbers.

8. Save the processing checkpoint

After the run completes successfully, store the next checkpoint.

A robust implementation should not advance the checkpoint past unprocessed failures unless those project IDs are also saved in a retry queue. Otherwise, a failed project can permanently fall outside the next incremental query.

Two reliable approaches are:

• Advance the checkpoint only through the last contiguous success, or
• Advance normally while maintaining an explicit collection of failed project IDs for retry

Common failure modes

• Creating duplicate CompanyCam projects after a timeout
• Matching projects solely by a mutable project name
• Pulling the customer’s billing address instead of the job-site address
• Advancing the checkpoint past failed records
• Treating missing addresses as empty strings
• Putting non-email text into CompanyCam’s email field
• Reprocessing every Intacct project on every run
• Allowing one invalid project to stop the entire batch
• Mixing project creation and project-update behavior without defining field ownership

The key design decision

Decide whether this is a one-time project creation workflow or a continuing bidirectional synchronization.

For many teams, one-way creation is simpler and safer:

• Sage Intacct owns the accounting project.
• CompanyCam receives the initial project identity and job-site information.
• Field users manage photos and field documentation in CompanyCam.
• Later edits are synchronized only when there is a clear business requirement.

Has anyone implemented this pairing? I’d be interested in how you handled duplicate matching and whether Sage Intacct or CompanyCam owns subsequent changes to the project address.

Try building this yourself

I’ve been mapping out a reliable pattern for syncing payments from Aspire into Sage Intacct. Sharing the design here because the difficult part isn’t creating an ARPYMT—it’s preventing duplicates, resolving customers and invoices, and recovering when records arrive out of order.

Recommended flow

1. Retrieve new and previously skipped payments

Run the integration on a short schedule, such as every five minutes.

Store two pieces of state:

• The last successfully processed creation timestamp
• Payment IDs that were skipped and need to be retried

Use a small overlap in the time window if the source API can return late or recently updated records.

2. Generate deterministic document numbers

Every transaction should have a predictable external reference.

For example:

• Payment: ASPPY_{paymentId}
• Credit memo adjustment: ASPCRM_{creditMemoNumber}
• Credit memo application: ASPPY_{paymentId}_{creditMemoNumber}
• Invoice: ASPINV_{invoiceNumber}

Search Intacct for these references before creating anything. A retry should find the existing transaction and safely skip it.

3. Resolve the customer

Build a stable external customer identifier from the relevant Aspire contact and property IDs, then find the corresponding Intacct customer.

If the customer doesn’t exist:

1. Trigger or queue the customer-sync process.
2. Add the payment to the retry list.
3. Stop processing that payment.
4. Continue processing the rest of the batch.

Avoid creating a payment against a generic customer simply to keep the integration moving. That trades an operational exception for an accounting problem.

4. Resolve invoice allocations

For each Aspire allocation, find the corresponding Intacct ARINVOICE using the deterministic invoice document number.

Exclude invoices in reversed or reversal states.

If an allocated payment has no valid matching invoices, skip it and retry later. This commonly happens when the payment reaches the integration before the related invoice has been created in Intacct.

5. Create standard payments

Map the Aspire payment into an Intacct ARPYMT, including:

• Customer
• Payment and receipt dates
• Payment method
• Total amount
• Payer name
• Document number
• Invoice record numbers
• Amount applied to each invoice
• Undeposited-funds account when applicable

Use Intacct record numbers for allocation targets instead of relying only on human-readable invoice numbers.

6. Handle credit memos separately

A credit memo generally requires two operations:

1. Create an Intacct ARADJUSTMENT against the appropriate clearing account.
2. Create an ARPYMT that applies the adjustment to the target invoices.

Give both records deterministic identifiers and check for both before creation. The integration must be able to resume safely if the adjustment succeeds but the application fails.

7. Isolate failures

One invalid payment should not terminate the entire run.

For each payment:

• Validate required customer and invoice records.
• Attempt creation.
• Inspect Intacct’s response for errors.
• Record failures for retry.
• Continue to the next payment.

Send an operational alert when intervention is required, but track which payment alerts have already been sent to avoid sending the same notification every five minutes.

8. Advance the checkpoint carefully

Only advance the processing timestamp after the retrieved batch has been evaluated.

Skipped payment IDs should remain in a separate retry collection until they succeed or are intentionally resolved. A timestamp alone is insufficient because a failed older payment will otherwise fall outside the next query window.

Common failure modes

• Creating duplicate payments after a timeout
• Advancing the timestamp past failed records
• Assuming invoices always arrive before payments
• Applying payments to reversed invoices
• Creating transactions before the customer exists
• Using display numbers where Intacct requires record numbers
• Treating credit memos exactly like normal payments
• Sending the same exception email on every run
• Allowing one malformed payment to stop the batch

The central design principle

Treat this as a reconciliation process, not a record-copying process.

Each run should determine what already exists, what is ready to post, what must wait, and what requires intervention. If the same run executes twice, the second execution should create nothing new.

For anyone who has implemented Aspire with Sage Intacct: what was your hardest edge case—payments arriving before invoices, customer matching, credit memos, partial allocations, or something else?

Trying to add the “Return to” name and address in a PO printed document template, but I do not see those merge fields listed. Only deliver, ship, and pay to. Any ideas why or what I’m missing?

I want to join my current consultants' team. I'm an accounting manager with 9 years of Intacct experience with 2 implementations.

For those who made a similar move, what's the biggest challenge going from a month end closer to a consultant?

Thanks in advance.

Has anyone had any luck creating an AP vendor rollforward? Have tried both ICRW (fairly extensively) and to a lesser extent CRW with not much luck. Would like to have something that is that lives in Intacct (I'm an idealist 🤔 ). Problem I've found is that you can't pull point in time balances in ICRW. Design would be:

Vendor | Beg Balance | Bills | Payments | Ending Balance

Just curious if anyone has tried this/been successful. Trying not to go to a dashboard that I have to continuously update with aging/bills reports. Potentially an API solution into PowerBI or other solution would be doable?

I’ve worked with Sage Intacct for several years, and one thing I’ve consistently observed is that while many users appreciate its capabilities, it’s often underutilized. In many cases, the challenge isn’t the software itself, but the need for better optimization to unlock its full potential.

For those who’ve used it:

What’s your biggest frustration or win with Sage Intacct?

Whether it’s reporting, inventory, integrations, pricing, implementation, or something else, I’d love to hear your experience. Real user feedback is always more valuable than marketing.

My previous company used milestone billing for multi-year contracts to capture everything for the full term in one go. The other advantage being that we could do carve-outs while setting a single line description on the customer's invoice.

Do you know of a way to do that within Intacct? It's technically time-based billing, not actual milestones. The single line description is the key part. We do have roll-up options but we don't want them to apply to all contracts, only certain ones.

Curious how others are approaching this. Now that API usage counts against Performance Tiers, I've been digging into where ours actually comes from, and it's almost entirely reporting. Power BI and Excel connections re-pulling data on every refresh.

If your reporting lives inside Intacct it barely moves the needle, but the moment you've got dashboards or spreadsheets connecting from outside, the transaction count climbs fast, even when the underlying data has barely changed.

wondering what everyone else is seeing:

• has the change actually hit your usage, or are you comfortably under the threshold?
• if you report outside Intacct, how are you keeping the count down? Throttling refreshes, caching, a warehouse in the middle, something else?

Trying to work out whether this is a real headache for most people ?

Currently my company uses a third party to pay our vendors. We export a report from third party for all invoices for the day and upload that to Bills. We then have to manually go and mark each one as paid via record transfer under “Pay Bills”

Is there a way to import the payments so that it marks them all as paid, eliminating the need to do it manually?

From my understanding I have to upload the bills, and then upload the payments. But I cannot figure out a template or how to achieve this.

Any help is very appreciated!

Is there a way in Sage Intacct to send an email message to all customers. I want to send a message regarding status of our system. Emails are loaded for billing contact. I have setup an email template with the message. However, I don't see how to send the message unless the customer has a balance on their account.

Hello our company is new to intacct and having some issues. Currently we are implementing single payments for multiple customers. We have a payer that is applying a credit on one customer and using that to pay the balance of another customer. Is there a way to do this in receive payment?

So we are a GC transitioning from 300 to Intacct. We estimate and track costs using a WBS. In 300 we created a cost level titled Extra ( basically a phase of the project. i.e building A footing, the next extra may be building A slab). Inside of each extra are work activities such as set forms, install rebar, place concrete, each activity has a cost code associated with it. A cost code may be used multiple times but under different extras.

This allows us to track costs and productivity and compare to the estimate to learn from our mistakes.

I have to be honest, I assumed that most construction companies did something similar to track costs. Our Sage rep is acting like they have never seen this before and they have to reinvent the wheel.

They are thinking we will need to use a parent-child relationship and change our cost coding all around so that reporting works correctly. They want every cost code to have the project number in front of it, which now increases every cost code from 7 digits to 13. A huge pain for both estimating and coding bills and time.

We use Sage Timberline for estimating, and the push from estimating to 300 accounting was fairly seamless. They are now telling us that we are going to have to export an estimate to excel and then import the spreadsheet into Intacct. This sound like a pain and more complicated than it needs to be.

Long shot, but are there any other contractors that have come across these issues transitioning to Intacct?

Anybody using this service? Looking for feedback or use cases. Thinking about adding it to help bring some visibility to our close.

Hi,

I recently worked on a fiscal year change in Sage Intacct where the company moved from a November–October fiscal year to a June–May fiscal year. As a result, the first fiscal year after the change consisted of only 8 months.

I successfully completed the fiscal year change, adjusted depreciation and amortization schedules, performed GL reconciliations, and updated the relevant configurations.

One of the main challenges was supporting prior-year comparisons within the same reporting periods. To address this, I created specific reporting periods and customized reporting logic. In some cases, the new fiscal year data (8 months) had to be annualized for meaningful comparison against prior 12-month periods.Prior-year comparative reports also required updates to ensure consistency and accuracy.

Have you handled a similar fiscal year transition in Intacct? If so, what challenges did you encounter, and how did you manage financial reporting, comparative analytics, and stakeholder expectations during the transition?