Integrations

Quick Payable keeps invoice, vendor, and payment data aligned between Salesforce and the other systems your finance team relies on. This guide covers connecting an ERP or accounting system, what actually syncs, API access for custom integrations, and CSV import/export as a fallback.

Supported Integration Types

• ERP and accounting system sync: connects Quick Payable with systems to keep invoice, vendor, and payment data aligned.
• Salesforce API access: because Quick Payable is 100% Salesforce-native, it's reachable through Salesforce's own REST, SOAP, and Bulk APIs for custom or middleware-based integrations.
• Excel and CSV import/export: a straightforward fallback for systems that don't have a direct connection, or while a direct integration is still being set up.

Connecting an ERP or Accounting System

The exact configuration screens vary by system, but the overall process looks similar across ERPs:

1. Gather the credentials or connected app details your ERP or accounting system requires for an external integration.
2. Work with your implementation team to map Quick Payable fields (invoice number, vendor, amount, GL code, cost center) to the equivalent fields in your target system.
3. Run a small test batch of invoices through the connection before relying on it for full volume.
4. Confirm data flows in both directions as expected, approved invoices moving out, and status or payment confirmation moving back in in if your setup supports it.

What Data Syncs

• Approved invoice data, including amounts, line items, and GL coding.
• Vendor records, including contact details and payment terms.
• Payment status, so Quick Payable reflects whether an invoice has actually been paid once your accounting system processes it.

Exactly what syncs, and in which direction, depends on how your specific ERP connection is configured. Confirm the details of your setup with your implementation contact rather than assuming full two-way sync by default.

Field Mapping Considerations

• GL codes and cost centers: confirm your chart of accounts structure matches between systems before go-live, mismatches here cause the most reconciliation headaches later.
• Vendor identifiers: decide whether vendor records are matched by name, tax ID, or an internal vendor ID, and keep that identifier consistent across systems.
• Currency and tax fields: confirm how multi-currency or tax-inclusive amounts are represented in both systems if you operate across regions.

Using the Salesforce API for Custom Integrations

Because Quick Payable does not maintain a separate, standalone API, custom integrations work through the same Salesforce API layer as the rest of your org.

• Salesforce REST, SOAP, and Bulk APIs can read and write Quick Payable's invoice, vendor, and approval records like any other Salesforce object.
• Platform Events can trigger external systems when key AP events happen, such as an invoice being approved.
• Middleware and integration platforms that already connect to Salesforce, such as MuleSoft or a similar iPaaS tool, can integrate with Quick Payable without a separate connector.

Excel and CSV Import and Export

• Export approved invoices, vendor records, or reporting data to CSV for systems without a direct connection.
• Import vendor lists or historical data in bulk using standard Salesforce data import tools.
• This is a reasonable way to operate before a direct ERP connection is set up, and doesn't lock you out of connecting a system later.

Testing an Integration

1. Test with a small, realistic batch of invoices rather than your full volume on day one.
2. Confirm field mapping is correct before scaling up, especially GL codes and vendor identifiers.
3. Watch the first few real syncs closely so any mismatch is caught early rather than discovered during reconciliation weeks later.