Skip to main content
A bill enters the bill pay pipeline automatically as soon as it’s processed by Nectar — as long as your company has Bill Pay enabled. You don’t need to take any action to trigger it. Every new bill that comes through a connection, upload, or manual entry is evaluated.
If no rules match, the bill enters a Pending routing state. From there, one of two things happens:
  • If you’ve configured a catch-all destination, the bill is automatically forwarded there.
  • If there’s no catch-all, the bill waits until it’s manually assigned to a destination or a matching rule is created.
You can check for unmatched bills in the Funding overview by filtering for “Pending routing” status.
Yes. If multiple routing rules match the same bill and they point to different destinations, the bill is sent to all of them. Delivery is deduplicated — if two rules both point to the same destination, the bill is only delivered once.You can also manually send a bill to an additional destination from the Routing history page without undoing the original routing.
  • Deleted bill: The payment cycle is cancelled. If payment was already in-flight (funding requested or processing), the cycle is flagged for manual reconciliation.
  • Revised bill: The old cycle is cancelled and a brand-new cycle is created for the revised version. The new bill goes through the full evaluation process again.
  • Charges change: If payment hasn’t started, the updated amount is noted. If payment is in-flight, the change is flagged for attention.
Bills approaching their due date show a late-risk badge in the Funding overview table. The badge color indicates severity:
  • Warning — due date is approaching (early alert)
  • Urgent — close to due date
  • Critical — due date is imminent or has passed
Nectar also sends email notifications at each escalation tier to the users configured in your routing rules.
These are temporary pause states:
  • In exception means an issue was raised that requires attention before the bill can continue through the pipeline. Once resolved, the bill resumes from where it left off.
  • In dispute means a formal dispute was opened against the bill (for example, contesting incorrect charges with the utility). The cycle pauses until the dispute is resolved.
Neither state is terminal — bills return to their prior position once the exception or dispute is cleared.
GL codes can be assigned in two ways:
  1. Automatically by GL coding rules — if you’ve configured rules with “Assign GL code” actions, matching bills receive the GL code during evaluation.
  2. Manually — from the Routing history detail panel, you can edit the GL code for any non-terminal bill.
GL coding rules are evaluated before routing rules, so a bill can receive its GL code and be routed in a single pass.
Yes. The rule builder includes a dry-run preview that evaluates your rule against recent bills without actually routing anything. You’ll see which bills would have matched and what actions would have fired. This is the safest way to verify new rule logic before turning it on.
Nectar currently supports integrations with:
  • QuickBooks Online (full OAuth flow)
  • SAP S/4HANA
  • Oracle Fusion
  • Workday Financials
  • NetSuite
Each integration is set up through a guided wizard from the Destinations page.
You have a few options:
  • Pause a destination — stops delivery to that specific destination while keeping rules active. Bills will still be evaluated but delivery to that destination is held.
  • Deactivate a rule — stops a specific rule from matching. Other rules continue working.
  • Contact support — if you need to pause the entire bill pay pipeline, reach out to [email protected].
Nectar’s operations team reviews bills after validation to ensure data quality before they’re routed to your AP systems. This review step catches any remaining issues — like illegible scans or unexpected formatting — before bills reach your accounting team.