0:06 — Introductions and what Bank Pay is — Nick Arkins opens the webinar and introduces Tammy Bower as the presenter. He defines Bank Pay as banking and payment functionality available in 180 countries that consolidates outgoing payments, payment tracking, and global banking while keeping the customer’s existing bank relationships. 1:44 — Product suite and partner positioning — Bank Pay can be combined with the full procure-to-pay lineup, from procurement through PaperSave invoicing, or used standalone if only payments are needed. Nick notes the offering is open to all customers and that the company received a 2024 Blackbaud integration partner award. 1:57 — Why Bank Pay matters — Nick summarizes the value points: cash in one place, transaction automation across check, ACH, and wire, same-day supplier payment, payments processed right after invoice approval, and no manual downloading and uploading of payment batch files. He contrasts paying through your existing bank with solutions that use third-party non-banking providers, which he frames as fraud exposure. 3:12 — Demo start: PaperSave homepage and workflow — Tammy begins the demonstration with an overview of the PaperSave homepage tiles, noting customers may have some, all, or just Bank Pay depending on what they own. She opens a workflow diagram and explains the demo will start at the last step of the invoice approval process. 5:00 — Two entry paths into payment approval — When a user hits submit on the final approval step, the invoice transaction is created in Financial Edge NXT and the document moves to payment processing. Customers not using PaperSave’s AP automation can instead have invoice transaction data pulled from Financial Edge NXT into the same payment workflow. 5:32 — Batch building and approval rules — Tammy contrasts typical batch building — done in or outside the ERP with no audit trail of who approved it and no way to reject individual items — with a workflow where a user builds a batch, sends it for approval, and rules escalate items by dollar amount or by coding such as fund or grant to additional approvers. Once the required approval levels are complete, Bank Pay communicates with the bank using the vendor payment and routing information. 7:26 — Submitting an invoice to Financial Edge NXT — Working from her workflow view of 60 invoices totaling just over $101,000, with 44 waiting in payment review, Tammy submits a Resnet invoice. PaperSave creates the invoice transaction in Financial Edge NXT immediately, and she opens the payables record to show the new transaction, the PaperSave tile, and the source document with a creation time matching the moment she submitted. 9:56 — Filtering and building the payment batch — Tammy describes the manual alternative — printing a payment journal, marking up rejections, removing them, printing and re-routing checks for signatures — then shows filtering the payment review list of 31 invoices by due date down to 11, with quick measures updating to show total, largest, and oldest. Filters can also be applied by dollar amount, bank account, or a combination. 13:00 — Approver review, reject, and escalation — The batch is sent to an approver who receives an email notification. The approver can filter to review only invoices above a threshold, see who approved each item and the coding used, approve items one at a time, or reject an item with a required comment that sends it back to the queue. Invoices over $1,000 then route to a second, executive approval level. 17:26 — What happens after final approval — After the last approval, the data goes in two directions: to Bank Pay, which validates vendor remit-to addresses and routing information, compiles the file, and sends it to the bank; and to a pending payment file that waits for that validation before marking the invoices as paid in Financial Edge NXT, typically within five to about twenty minutes. Batches can span multiple bank accounts, payment types, vendors, and countries. 17:35 — Paid invoices and workflow write-back — Tammy filters her invoices by paid to show a completed example: the invoice transaction marked paid, the payment transaction information, and the document. Each payment gets an ID that is written into the workflow along with fields for paying bank account, payment method, creation date, and status — in process versus settled, where settled means the supplier received the funds — and the payment ID appears in the completed step of the workflow as a filterable profile field. 19:57 — Inside the Bank Pay portal — Tammy logs into the Bank Pay portal, noting that Pairsoft has multiple suite products much as Blackbaud has FE NXT, RE NXT, and BBCM. She reviews sent batches: each batch receives a batch payment ID (1029 in the example) and each individual payment receives its own payment ID, referred to as a check number, which corresponds to the workflow audit trail and profile fields. All the information is pulled from Financial Edge NXT as the data source. 22:42 — Multi-invoice payments and fund withdrawal — A single payment covering several invoices — shown with a PPG Architectural example — carries one check number with each invoice listed individually, while vendors requiring one payment per invoice can be set up that way. Customers control payment method per vendor, can submit a full batch or reject individual items, and funds are drawn from the bank as individual payments rather than a lump sum, with no 24-hour hold: money leaves when a wire is processed or a check is cashed. 24:56 — Historical dashboard and audit trail — Tammy shows a historical dashboard that drills into payments by year, quarter, or month, opening a $32,000 group of late or past-due payments to view the underlying invoices, which can be shared by email. She closes on the end-to-end audit trail: who approved the invoice and when, the transaction created in Financial Edge NXT, who approved the payments, the payment process ID, and how and when each item was paid and cleared.

Home / Resources / Webinars

Demo: Bank Pay in PaperSave for Blackbaud Financial Edge NXT

Key takeaways

PaperSave Bank Pay is a payment solution from Pairsoft that sends payment files through your own existing bank rather than a third-party non-banking provider, and is described as available in 180 countries.
Payment approval happens inside the PaperSave workflow: a user builds a batch of approved invoices, filters it by criteria such as due date, dollar amount, or bank account, and routes it to one or more approvers based on configurable rules.
Once the last approval is given, the data moves in two directions — to Bank Pay to compile and validate the bank file, and to a pending payment file that marks the invoices as paid in Financial Edge NXT, typically within about 5 to 20 minutes.
Bank Pay supports check, ACH, and wire payments, domestic and international, and can pay out of multiple bank accounts within a single batch.
Bank Pay works with PaperSave’s AP invoice automation as an extension of the existing approval workflow, or as a standalone product that pulls invoice transactions directly from Financial Edge NXT.
Every batch receives a batch payment ID and every individual payment receives its own payment ID (referred to as a check number), which is written back into the workflow profile fields for reconciliation and audit.
Funds are withdrawn as individual payments when a check is cashed or a wire is processed, rather than being pulled as a lump sum or held for a 24-hour period.

Overview

This webinar covers Bank Pay, the payments component of the Pairsoft (PaperSave) procure-to-pay suite, demonstrated for organizations using Blackbaud Financial Edge NXT. Nick Arkins opens with a short positioning segment, describing Bank Pay as banking and payments functionality available in 180 countries that keeps payments, payment tracking, and global banking in one place while preserving the customer’s existing bank relationships. He notes that Bank Pay can be combined with the broader procure-to-pay lineup — procurement and the PaperSave AP invoice automation product — or bought on its own, that it is open to all customers, and that Pairsoft received a 2024 Blackbaud integration partner award. The main contrast he draws is against payment solutions that route money through third-party non-banking providers, which he frames as added fraud exposure; Bank Pay instead integrates directly with the customer’s bank connection.

Tammy Bower then runs the demonstration, starting at the end of the AP approval process rather than the beginning. In PaperSave’s workflow, the final approval step submits the document to Financial Edge NXT, which creates the invoice transaction in real time — she shows an invoice named Resnet moving from submit to a created transaction in FE NXT within seconds, with the source document visible as a PaperSave tile on the transaction. Organizations that do not use PaperSave’s AP automation can instead have Bank Pay pull existing invoice transaction data out of Financial Edge NXT into a document so the same payment workflow applies.

The payment approval workflow is the core of the demonstration. Rather than building a payment batch in the ERP or outside it with no audit trail, a user works from a payment review queue — Tammy’s demo shows 60 invoices in workflow totaling just over $101,000, with 44 sitting in payment review — and filters the list by due date, dollar amount, vendor, or bank account to select what to pay. Quick measures update as filters are applied, showing totals, the largest invoice, and the oldest. The batch is then sent to an approver, who is notified by email and can review items selectively, seeing who approved each invoice, when, and the GL coding used to create the FE NXT transaction. Individual items can be approved or rejected — rejection requires a comment and returns the item to the queue — instead of forcing the whole batch to be redone. Rules can escalate items by dollar amount or by coding such as fund or grant to additional approvers; in the demo, invoices over $1,000 route to a second executive approval level.

After final approval, the work of printing, signing, stuffing, and mailing checks is handled downstream. The data splits: one path goes to Bank Pay, which verifies vendor payment information — remit-to address for checks, routing information for electronic payments — compiles the file, and sends it to the bank; the other path goes to a pending payment file that waits for that validation and then marks the invoices as paid inside Financial Edge NXT, generally in five to about twenty minutes depending on file size. The Bank Pay portal shows each batch with a batch payment ID and each payment with its own payment ID or check number; a payment covering several invoices for one vendor lists those invoices individually, and vendors who require one payment per invoice can be handled that way too. Payment status fields — paying bank account, payment method, creation date, in-process versus settled, and the reconciliation/payment ID — are written back as filterable profile fields in the PaperSave workflow.

Tammy closes by noting that funds leave the account as individual payments when each check is cashed or each wire is processed by the bank, not as a held lump sum, and that multiple bank accounts and payment types can be mixed in one batch. She also shows a historical dashboard that drills into paid activity by year, quarter, or month — for example opening a $32,000 group of late or past-due payments to see the underlying invoices — and can share that information by email. The combined result she emphasizes is a single audit trail spanning invoice approval, transaction creation in Financial Edge NXT, payment approval, payment ID, and how and when each item was paid and cleared.

Chapters

0:06 — Introductions and what Bank Pay is — Nick Arkins opens the webinar and introduces Tammy Bower as the presenter. He defines Bank Pay as banking and payment functionality available in 180 countries that consolidates outgoing payments, payment tracking, and global banking while keeping the customer’s existing bank relationships.
1:44 — Product suite and partner positioning — Bank Pay can be combined with the full procure-to-pay lineup, from procurement through PaperSave invoicing, or used standalone if only payments are needed. Nick notes the offering is open to all customers and that the company received a 2024 Blackbaud integration partner award.
1:57 — Why Bank Pay matters — Nick summarizes the value points: cash in one place, transaction automation across check, ACH, and wire, same-day supplier payment, payments processed right after invoice approval, and no manual downloading and uploading of payment batch files. He contrasts paying through your existing bank with solutions that use third-party non-banking providers, which he frames as fraud exposure.
3:12 — Demo start: PaperSave homepage and workflow — Tammy begins the demonstration with an overview of the PaperSave homepage tiles, noting customers may have some, all, or just Bank Pay depending on what they own. She opens a workflow diagram and explains the demo will start at the last step of the invoice approval process.
5:00 — Two entry paths into payment approval — When a user hits submit on the final approval step, the invoice transaction is created in Financial Edge NXT and the document moves to payment processing. Customers not using PaperSave’s AP automation can instead have invoice transaction data pulled from Financial Edge NXT into the same payment workflow.
5:32 — Batch building and approval rules — Tammy contrasts typical batch building — done in or outside the ERP with no audit trail of who approved it and no way to reject individual items — with a workflow where a user builds a batch, sends it for approval, and rules escalate items by dollar amount or by coding such as fund or grant to additional approvers. Once the required approval levels are complete, Bank Pay communicates with the bank using the vendor payment and routing information.
7:26 — Submitting an invoice to Financial Edge NXT — Working from her workflow view of 60 invoices totaling just over $101,000, with 44 waiting in payment review, Tammy submits a Resnet invoice. PaperSave creates the invoice transaction in Financial Edge NXT immediately, and she opens the payables record to show the new transaction, the PaperSave tile, and the source document with a creation time matching the moment she submitted.
9:56 — Filtering and building the payment batch — Tammy describes the manual alternative — printing a payment journal, marking up rejections, removing them, printing and re-routing checks for signatures — then shows filtering the payment review list of 31 invoices by due date down to 11, with quick measures updating to show total, largest, and oldest. Filters can also be applied by dollar amount, bank account, or a combination.
13:00 — Approver review, reject, and escalation — The batch is sent to an approver who receives an email notification. The approver can filter to review only invoices above a threshold, see who approved each item and the coding used, approve items one at a time, or reject an item with a required comment that sends it back to the queue. Invoices over $1,000 then route to a second, executive approval level.
17:26 — What happens after final approval — After the last approval, the data goes in two directions: to Bank Pay, which validates vendor remit-to addresses and routing information, compiles the file, and sends it to the bank; and to a pending payment file that waits for that validation before marking the invoices as paid in Financial Edge NXT, typically within five to about twenty minutes. Batches can span multiple bank accounts, payment types, vendors, and countries.
17:35 — Paid invoices and workflow write-back — Tammy filters her invoices by paid to show a completed example: the invoice transaction marked paid, the payment transaction information, and the document. Each payment gets an ID that is written into the workflow along with fields for paying bank account, payment method, creation date, and status — in process versus settled, where settled means the supplier received the funds — and the payment ID appears in the completed step of the workflow as a filterable profile field.
19:57 — Inside the Bank Pay portal — Tammy logs into the Bank Pay portal, noting that Pairsoft has multiple suite products much as Blackbaud has FE NXT, RE NXT, and BBCM. She reviews sent batches: each batch receives a batch payment ID (1029 in the example) and each individual payment receives its own payment ID, referred to as a check number, which corresponds to the workflow audit trail and profile fields. All the information is pulled from Financial Edge NXT as the data source.
22:42 — Multi-invoice payments and fund withdrawal — A single payment covering several invoices — shown with a PPG Architectural example — carries one check number with each invoice listed individually, while vendors requiring one payment per invoice can be set up that way. Customers control payment method per vendor, can submit a full batch or reject individual items, and funds are drawn from the bank as individual payments rather than a lump sum, with no 24-hour hold: money leaves when a wire is processed or a check is cashed.
24:56 — Historical dashboard and audit trail — Tammy shows a historical dashboard that drills into payments by year, quarter, or month, opening a $32,000 group of late or past-due payments to view the underlying invoices, which can be shared by email. She closes on the end-to-end audit trail: who approved the invoice and when, the transaction created in Financial Edge NXT, who approved the payments, the payment process ID, and how and when each item was paid and cleared.

Questions this webinar answers

What is PaperSave Bank Pay?

Bank Pay is the banking and payments component of the Pairsoft procure-to-pay suite. It handles outgoing payments, payment tracking, and global banking in one place, is described as available in 180 countries, and sends payment files through the customer’s own existing bank rather than through a third-party payment provider.

Do I have to use PaperSave’s AP invoice automation to use Bank Pay?

No. Bank Pay can run as a standalone product. If PaperSave’s AP automation is already in place, payment approval is simply an extension of the existing invoice approval workflow — instead of moving to a completed or entered step, the document moves into the payment approval workflow. If it is not in place, Bank Pay pulls invoice transactions that were manually created in Financial Edge NXT and brings that data into a document so the same filtering and approval workflow applies.

What payment methods and geographies are supported?

Check, ACH, and wire payments are supported, and a single batch can include different payment types, different vendors, and payments made nationally or internationally. Payments can also be drawn from multiple bank accounts within the same batch, rather than being limited to a single paying account.

How does a payment batch get built and approved?

A user works from a payment review queue containing invoices that have been approved (or whose data was pulled from Financial Edge NXT) and filters the list by criteria such as due date, dollar amount, vendor, or bank account. Selecting a filter updates quick measures showing the total, the largest invoice, and the oldest. The resulting batch is sent to an approver, who receives an email notification. The approver can review items selectively — for example only those above a dollar threshold — see who approved each invoice and when, and view the GL coding used to create the transaction. Individual items can be approved or rejected without redoing the whole batch, and rejection requires a comment before the item returns to the queue.

Can approvals be escalated based on dollar amount or account coding?

Yes. Rules can route a payment request to additional approvers based on a dollar amount or on coding such as a fund or a grant, so that two or three people must approve. In the demonstration, invoices over $1,000 automatically moved to a second, executive-level approval queue after the first approval.

How quickly does an approved invoice appear in Financial Edge NXT, and when is it marked paid?

When the final AP approver submits an invoice in PaperSave, the invoice transaction is created in Financial Edge NXT in real time — in the demonstration, the transaction appeared with a creation timestamp matching the moment of submission, though it still has to be posted as normal. After payment approval, the invoices are marked as paid in Financial Edge NXT once Bank Pay finishes validating and compiling the bank file, which generally takes somewhere between five and about twenty minutes depending on the size of the file.

How does reconciliation work?

Each payment batch receives a batch payment ID, and each individual payment within it receives its own payment ID, referred to as a check number. That payment ID is written back into the PaperSave workflow as a filterable profile field, along with the bank account the payment came from, the payment method, the creation date, and the status. Status shows as in process until the funds reach the supplier, at which point it shows as settled. The payment ID also appears on the document in the completed step of the workflow.

If one payment covers several invoices for the same vendor, how is that shown?

The payment carries a single check number or payment ID, and each of the invoices included in that payment is listed individually beneath it in the validation view. If a vendor requires a separate payment for every invoice, that can be configured instead — the customer controls how each vendor is paid.

When is money actually withdrawn from the bank account?

Funds are drawn out of the bank as individual payments rather than as a lump sum, and there is no 24-hour holding period. A wire leaves the account once it hits the bank and the bank processes it, and a check amount is withdrawn once the vendor cashes the check.

What reporting is available?

Along with the current payments view, there is a historical dashboard that drills into paid activity by year, quarter, or month. In the demonstration it was used to open a group of roughly $32,000 in late or past-due payments and view the underlying invoices processed and completed in that period, and that information can be shared by email. Combined with the workflow records, this provides an audit trail covering who approved an invoice and when, the transaction created in Financial Edge NXT, who approved the payment, the payment process ID, and how and when each item was paid and cleared.

Table of Contents

Get A Demo:

Simple solutions. Powerful results. Seamlessly integrated.

Get a PairSoft Demo