How to automate expense management in Blackbaud Financial Edge NXT

Key takeaways

• In Financial Edge NXT, a card charge is only finished when its distribution names the account, the project and, for restricted money, the grant.
• Blackbaud's Expense Management gives non-financial staff an Expenses tab, approval groups and expense categories with account defaults.
• Credit card feeds bring issuer transactions in; someone still decides the distribution for anything the defaults do not cover.
• Vergo proposes the full distribution from how your team coded similar spend, and texts cardholders for receipts.

Where should you go next?

• Vergo's Blackbaud Financial Edge NXT integration
• What expense management software integrates with Blackbaud Financial Edge NXT?
• Get started with Vergo

How do you automate expense management in Financial Edge NXT, step by step?

1. Connect Financial Edge NXT. Vergo connects through Blackbaud's SKY API, reads your chart of accounts, and posts coded spend into Financial Edge NXT — invoices with the receipt attached, or journal entry batches. SKY API access is self-serve.
2. Connect your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change, including cards already on a Financial Edge NXT feed.
3. Collect receipts by text. Program staff and volunteers reply with a photo; employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
4. Propose the distribution. Vergo proposes account, project and grant for every line, and shows why each was chosen.
5. Review and deliver. The business office confirms, and the coded entry is posted into Financial Edge NXT, with its receipt.

What does a Financial Edge NXT distribution need?

• Account: the GL account from your chart.
• Project: the program or activity the spend supports.
• Grant: where the spend draws down a restricted award.
• Transaction codes: up to five, used like attributes for reporting.

Why do defaults stop short for nonprofits?

Expense categories in Financial Edge NXT carry account defaults, so "mileage" or "office supplies" lands on a sensible account. What a category cannot know is which grant a purchase belongs to. The same box of supplies is general operating on Monday and a restricted program cost on Tuesday. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — the account, project and grant — not just the vendor name on the header. A grant manager sees the reason next to each proposal, which is the evidence a funder audit asks for.

A practical example

A community health center runs three federally funded programs and a general fund on Financial Edge NXT. An outreach coordinator buys printed flyers and a team lunch on one card at a health fair. Vergo texts for the receipt, proposes the printing line to the outreach program's grant and project, and the lunch to unrestricted staff meals, because that is how the last two health fairs were split. The finance manager confirms both lines, and the entry is posted to Financial Edge NXT with the receipt attached.

How Vergo handles this

Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. For fund accounting, that history includes which grants your team charged for similar purchases, so restricted spend is proposed to the right award instead of defaulting to operating. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.