Destination types
Email destinations
Forward bills to one or more email addresses. Each destination can include multiple recipients — useful for team inboxes or shared AP queues.
AP/ERP integrations
Push coded invoices directly to your accounting system. Supported systems include SAP S/4HANA, Oracle Fusion, Workday Financials, NetSuite, and QuickBooks Online.
Creating an email destination
Add email addresses
Type each email address and press Enter to add it. You can include as many recipients as needed. All recipients receive the same forwarded bill.
Connecting an ERP system
Select your ERP system
Choose from the available accounting systems: SAP S/4HANA, Oracle Fusion, Workday Financials, NetSuite, or QuickBooks Online.
Enter credentials
Provide a connection name and the required authentication details for your system. For QuickBooks Online, this launches an OAuth flow — you’ll sign in to your QuickBooks account and authorize Nectar to push invoices.
Managing destinations
From the destinations table, you can:- Edit a destination to update email addresses, credentials, or the connection name
- Pause a destination to temporarily stop deliveries without deleting it
- Resume a paused destination to restore deliveries
- Delete a destination you no longer need (rules referencing it will need updating)
Catch-all destination
You can mark one active destination as the catch-all. Any bill that doesn’t match a routing rule is automatically sent to the catch-all instead of sitting in a pending state. This ensures no bill falls through the cracks. To set a catch-all, click the star icon next to an active destination in the table, or configure it from the Rules page.If the catch-all destination is paused or deleted, unmatched bills will wait in Pending routing until you designate a new catch-all or manually assign them.
What gets delivered
When a bill is forwarded to an email destination, the recipient receives:- The bill PDF as an attachment
- Key details in the email body: vendor name, total charges, due date, service period, and line items (capped at 20)
Related pages
- Rules — configure the logic that routes bills to destinations
- Routing history — verify bills were delivered to the right place
- Glossary — Destination — definition