How do I set up a Sage Intacct AP payment run in Loopfour?
Loopfour's Sage Intacct integration creates payments through the APPAYMENT object, which pays one or more bills in a single run. Map a vendor, a bank or charge-card account, a payment method and date, then supply one payment-item entry per bill with its record key and amount — the same shape Sage Intacct's own legacy AP Payments API expects.
By Zuny Fester, Head of Operations and MarketingPart of the finance integrations guide.
| Object used | APPAYMENT (Sage Intacct's accounts payable payment object) |
|---|---|
| Multi-bill support | Yes — one payment run can apply against several bills at once via a payment-items array |
| Required fields | vendorid, a bank or charge-card account, at least one payment item, a payment date |
| API generation | Legacy XML Gateway object, kept for backward compatibility alongside Sage Intacct's newer APPYMT REST object |
What the connection actually does
Loopfour's Sage Intacct integration issues AP payments through the createApPayment action, which posts to Sage Intacct's legacy XML Gateway as an APPAYMENT record. Sage Intacct's own developer documentation confirms this object is provided for backward compatibility alongside a newer APPYMT object introduced in their REST API — Loopfour's integration targets the legacy object, which is still fully supported and is what the underlying XML request maps to field for field.
One payment run can cover several bills
An APPAYMENT isn't limited to a single bill. Sage Intacct's API accepts an array of payment-detail items, each naming a bill's record key and the amount to apply against it — matching exactly how Loopfour's integration builds the request. A single payment run can pay several outstanding bills for the same vendor in one call, which is closer to how a real AP payment batch actually works than paying bills one at a time.
What no other ERP in this matrix does the same way
QuickBooks has no exposed vendor-payment action at all in Loopfour's integration — bill status has to be checked and reconciled by other means. NetSuite has no dedicated payment object either; applying a payment goes through generic records. Sage Intacct is the only ERP here with a first-class, multi-bill payment object reachable directly through the integration, which is why a payment run belongs to its own connect page rather than being folded into a generic "how do I pay a bill" page that would be wrong for the other two.
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.
Field mapping
APPAYMENT request shape vs. Sage Intacct's documented fields
| Loopfour field | Sage Intacct XML field | Notes |
|---|---|---|
| vendorId | VENDORID | Required on every payment |
| bankAccountId | BANKACCOUNTID | A charge-card account is the alternative funding source |
| bills[].billKey / bills[].amount | APPYMTDETAILS (payment items array) | One entry per bill being paid in this run |
| paymentDate | PAYMENTDATE / CHECKDATE | Required |
Frequently Asked Questions
Sources
Related
Topic
AP & Invoice Processing
Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…
Read moreTopic
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…
Read moreDiagnostic
What breaks when there's no dedicated NetSuite payment action for Stripe reconciliation?
NetSuite has a dedicated Customer Payment record for applying payments to invoices, but Loopfour's NetSuite integration doesn't expose it as an action — matching a Stripe payout to NetSuite has to go through generic record search and create calls or SuiteQL instead of a purpose-built payment step, unlike Sage Intacct, QuickBooks, or Xero.
Read moreDiagnostic
What breaks when a Sage Intacct AP payment run fails partway through?
A Sage Intacct APPAYMENT run can pay several bills in one call. If a bad record key or a wrong amount on one line makes the whole run error, it's tempting to assume no bills were paid. That assumption is often wrong — the run can fail overall after already applying against some of the valid bills.
Read more