Skip to main content

AP Invoices in Sage Intacct

Agave AP Automation creates invoices in one of two places in Sage Intacct:

  • Purchasing transactions, for invoices with a project or a commitment. They land Pending, so your team can still review and post them. Committed invoices are converted from the PO or subcontract.
  • AP bills, for overhead invoices with no project and no commitment. Agave submits them, so they follow your Intacct approval setup.

Hover over a field on a Purchasing transaction to see what Agave writes:

  • Written
  • Written with a setting
  • Not written
Sage Intacct Purchasing transaction with its entries, with every field Agave writes outlined

Written

#Intacct fieldAgave fieldNotes
1Transaction typeSet by AgaveFrom your settings: one type each for PO invoices, subcontract invoices and invoices with no commitment.
2DateInvoice date
3GL posting dateGL posting date
4VendorVendor
8JobProjectThe sub job when every line shares one.
11Date dueDue date
13Vendor document numberInvoice number
14MessageDescription
19StateSet by AgaveAlways Pending, so your team can review and post it in Intacct.
20Cost CodeCost code
21Cost typeCost type
22Vendor (lines)Set by AgaveAlways the invoice vendor.
23Item IDItemComes from the cost type.
24MemoDescription
26QuantityQuantity
27UnitUnit of measure
28PriceUnit costIntacct works out the line amount from quantity and price.
Job (lines)ProjectThe line's sub job, else the line or invoice project.
Department (lines)Department

Written with a setting

#Intacct fieldAgave fieldNotes
10Payment termsPayment termsThe vendor's default terms, only when the invoice has no due date.
16AttachmentInvoice fileOnly when an attachments folder is set up for your Intacct connection.
25BillableBillableOptional setting. Also writes the project's customer.
Amount retained (lines)Retainage amountHeader retainage is split across the lines by amount.
Location (lines)Location (lines)The project's location, when you're connected at the top-level entity or by setting.
Converted from (lines)Commitment lineCommitted invoices only. Each line is converted from its PO or subcontract line.

Not written

#Intacct fieldNotes
5Pay toIntacct fills it from the vendor.
6Return toIntacct fills it from the vendor.
7Deliver to
9Document numberNumbered by Intacct.
12Reference
15Shipping method
17Txn currency
18Exchange rate fields
GL account (lines)Intacct takes it from the item.

Overhead invoices go to an AP bill instead:

  • Written
  • Written with a setting
  • Not written
Sage Intacct AP bill with its entries, with every field Agave writes outlined

Written

#Intacct fieldAgave fieldNotes
1DateInvoice date
2GL posting dateGL posting date
3VendorVendor
6Bill numberInvoice number
8DescriptionDescription
10Due dateDue date
16AccountGL account
17Transaction amountAmount
18DepartmentDepartment
21MemoDescription
24Vendor (lines)Set by AgaveAlways the invoice vendor.

Written with a setting

#Intacct fieldAgave fieldNotes
9TermPayment termsThe vendor's default terms, only when the invoice has no due date.
13AttachmentInvoice fileOnly when an attachments folder is set up for your Intacct connection.
20BillableBillableOptional setting.
23CustomerCustomerOnly on billable lines.
25ItemItemOnly when the line has an item.

Not written

#Intacct fieldNotes
4Pay toIntacct fills it from the vendor.
5Return toIntacct fills it from the vendor.
7Reference number
11Recommended to pay on
12Payment priority
14Place this bill on hold
15Retainage release
19LocationIntacct fills it from your entity.
22JobBills never carry a job. Invoices with a project become Purchasing transactions.
26Cost Code
27Cost type
28Quantity

Good to know​

  • Transaction types. Agave picks the Purchasing transaction type from your settings, one each for PO invoices, subcontract invoices and invoices with no commitment.
  • Tax and freight go in as their own lines, or are spread across lines by setting.
  • Attachments need an attachments folder set up for your Intacct connection.
  • Create only. Changes after sync are made in Intacct.
  • Need another field? Ask your Agave contact about custom field mapping.