Sage Intacct Unipay Release Notes
Unipay Release V2.0
August 6, 2025 | Product: Unipay
DESCRIPTION
The V2.0 Release includes the following new features and improvements. Application implementation and setup procedures have been updated.
RELEASE NOTES
New features:
Stripe as a payment processor
Stripe will now be available as a payment processor when configuring Unipay. The implementation process and configuration are the same across all payment processors. When setting up a new payment account within the middleware of the integration, Stripe will now be available in the drop-down.
Customer management moved to Intacct
Customer management, such as preferred payment method and Autopay enablement, has been moved to the Sage Intacct Customer record via a new object called Online Payments Customer Prefs. When a new customer is created within Sage Intacct, the application automatically generates this related object. The object can be viewed within the customer record by navigating to Accounts Receivable>Customers>View Customer> and scroll down to the bottom of the page. From this object, a user can enable autopay, update the payment method ID or mandate ID, provide the customer ID in the payment processor account, and more. With this change, the customer management in the Unipay middleware has been removed. A user will now manage customers within Sage Intacct. To learn more about the fields located in the Online Payments Customer Preferences, go to the Customer Management section of the help center, located here.
Invoice management moved to Intacct
Invoice management has not been moved to the Sage Intacct Invoice record via a new object called Online Payment Invoices Synchronization. When an invoice is generated in Sage Intacct, the application will automatically generate this related object. The object can be viewed within the AR invoice by navigating to Accounts Receivable>Invoices>View Invoice> and scroll down to the bottom of the page. From this object, a user can see if an invoice has synced to their payment processor, the status of the payment request for that invoice, manage how the payment request should be retried if it fails, and more. To learn more about the different fields and settings within the Online Payment Invoices Synchronization object, navigate to the Invoice management section of the help center located here.***
Stripe - Ability to select and pay multiple Invoices
When a customer selects Pay Now or the link located on the email from Autopay, they will be presented with the ability to add a payment method or use an existing payment method. Additionally, they can select multiple invoices to pay at once. This option is currently only available for instances where Stripe is the payment processor.
New Setting - Consolidate Payments
Within the Customer Record object (Online Payments Customer Prefs), located at the bottom of a customer record page in Intacct, the Consolidate Payments setting is available. When a user enables this setting for a customer, it creates a single payment request for multiple invoices with the same due date, transaction currency, and for the same customer.
New Setting - EFT Payment Interval
A new setting has been added within the middleware configuration called EFT Payment Interval. This setting allows a user to determine when the application should apply the payment back into Intacct for EFT payments. Below are the options:
Wait for Provider Response - The application will not apply the payment within Intacct until the webhook events have informed Unipay that the payment request has been processed.
0-10 - This is the option where a user can have the integration create the payment X number of days after a payment request is made. 0 means the application will create the payment in Intacct when a payment request is made to your payment provider. 1 means that 1 day after the payment request is made, the payment will be applied in Intacct. A user can choose X number of days, all the way up to 10.
New Setting - Pay Now Lookback Date
This setting allows a user to specify how far back the system can allow end customers to use the ‘Pay Now’ link on their invoices. In other words, any Pay Now links selected by customers for invoices due prior to this date will result in an error, and no payment request will be generated. This is to protect against potential duplicates when transitioning from a different payment processing service or for payment requests that have already been sent to your payment processor.
New Pay Now Link on Invoice in Intacct UI
A new Pay Now link has been added to the Sage Intacct Invoice UI. A user can now select this link, which will open a new window with the associated payment processor’s payment page. A user can then create a mandate or payment method and proceed to pay the selected invoice. To access this link, a user would navigate to Accounts Receivable>Invoices>View Invoice> Select Pay Now Link.
Merchant Logo
A new option has been added to the Payment Account Configuration screen in the middleware. Merchant logos will be visible in the top left corner of the ‘Pay Now’ screens that the end customer can see. The maximum file size allowed is 196Kb and the following file types are supported: jpg, .png, .webp, .svg.
Improvements:
Can now process payment requests for invoices in status - Partially Paid
With the addition of the Online Payment Invoice Synchronization object, the Unipay application can now sync over invoices that are in the Partially Paid status within Intacct. If an invoice is partially paid within accounts receivable, the integration will sync it to the payment provider or the remaining due amount on the invoice. Note, the system will still not accommodate any changes made to the invoice after it has synced to the payment provider.
Zero Days Before Due added as option for AutoPay - GoCardless
New value within has been added top the Days Before Due option in Autopay for GoCardless. The zero value can be selected to specify that Autopay should run and sync only invoices that are due or past due. By default, Payment Accounts configured with Stripe will run autopay and only pick up invoices on their due or past due invoices.
KNOWN ISSUES
N/A
APPLIES TO
The release is being deployed to all existing instances.
PREREQUISITES AND DEPENDENCIES
User has signed up and created an account within Unipay
Unipay’s package has been installed within the Sage Intacct Company
User has access to an account with one of the supported payment processors.
Proper permissions for the Unipay Web Services user within Sage Intacct company.
ACTIONS
The improvements and bug fixes included in this update are automatically applied to all Unipay customers’ Intacct Companies, so no further action is necessary. The Unipay setup and user documentation can be found in the Help Center. For details on any of the historical Unipay releases, please continue to the next section of this document. The next section provides important information to assist customers on understanding the changes and features added to the Unipay application.
Unipay V1.2
August 21, 2024 | Product: Unipay (GoCardless for Sage Intacct)
DESCRIPTION
Initial Release Notes: The following release notes are improvements and new features added in the V1.1 release of GoCardless for Sage Intacct.
New Features
Manual Mandate Migrations
A new tab has been added within a Payment Account called Mandate Upload. This section now allows users the ability to import existing GoCardless Mandates into the GoCardless for Sage Intacct application. This resolves the instances where a company is already utilizing GoCardless for payment processing and is now using GoCardless for Sage Intacct to initiate the mandate creation. Within this tab, a user can download a csv template, and import it back with the mandate information. Additionally, this screen will show a table of all previously imported Mandate files and their status.
Support for Order Entry
With the release of 1.2, GoCardless for Sage Intacct will now support Invoices generated from the Order Entry module. From within the Payment Account>Payment Account Details>Payment Connection Configuration screen, a new field called Include Order Entry Invoices has been added. When enabled, the system will include invoices that were generated from Order Entry and create a corresponding Accounts Receivable Invoice. The system will utilize the Order Entry Invoice ID as a reference. The GoCardless for Sage Intacct will support all payment methods for Order Entry Invoices. Additional permissions are required by the GoCardless for Sage Intacct Web User. Please refer to the User Guide and Setup Guide located in the Help Center for more details.
Pay Now Link for Order Entry
With the addition of Order Entry Invoices, a new Pay Now Link has been added to the application. The Pay Now link can be found via the Pay Now Hyperlink document located in the Help Center.
Improvements
Dynamic Localization
Users can now select the language utilized by the application. This will change the pages on the website to convert to the user's selected language. Additionally, the user has the ability to decide what language the emails sent to the customer should be in. Note, by default the Payment Account locale is English unless the user has a different country that belongs to a different locale.
Choose which Sage Customers to Sync
A workaround is now available for customers who don’t wish to sync all customers from the Intacct company. Users now can request a field be added to their Sage Intacct Customer Record called Sync to GoCardless. This field will serve as a flag informing the GoCardless for Sage Intacct application that this customer should sync over to GoCardless and invoice payments will be processed through GoCardless. When false, the GoCardless for Sage Intacct application will ignore that customer. This allows users to avoid having unnecessary customers synced to the middleware. To have this setting added, please request via support case before setup of your Payment Account or syncing customers to the GoCardless for Sage Intacct Application.
KNOWN ISSUES
A fix has been deployed regarding the issue with Character Limits on Payment Accounts. Customers should no longer run into an error when creating a Payment Account with more than 64 characters.
A fix has been made to the issue with the Transaction Amount on emails sent by GoCardless for Sage Intacct. The emails will now show the Transaction Amount based on the Transaction Currency within the Sage Intacct Invoice.
APPLIES TO
The entire release was applied to all users of GoCardless for Sage Intacct.
PREREQUISITES AND DEPENDENCIES
User has signed up and created an account within GoCardless for Sage Intacct.
User has access to a GoCardless Account.
Proper permissions for the GoCardless for Sage Intacct Web Services user within Sage Intacct company.
ACTIONS
The improvements and bug fixes included in this update are automatically applied to all GoCardless for Sage Intacct customers’ Intacct Companies, so no further action is necessary. The GoCardless for Sage Intacct User Guide is located in the Help Center. Please consult the Sage Intacct GoCardless for Sage Intacct Upgrade – System Changes and Features document available here. For details on any of the historical GoCardless for Sage Intacct releases, please continue to the next section of this document. The next section provides important information to assist customers on understanding the changes and features added to the GoCardless for Sage Intacct application.
Unipay Release V1.1
July 9, 2024 | Product: Unipay (GoCardless for Sage Intacct)
DESCRIPTION
Initial Release Notes: The following release notes are improvements and new features added in the V1.1 release of GoCardless for Sage Intacct.
New Features
Multiple Bank Accounts and Transaction Currencies
A user can now request to have multiple Bank Accounts assigned to a Payment Account in GoCardless for Sage Intacct. Each bank account can be assigned a specific transaction currency. The system will then create the payment within Sage Intacct against the correct bank account based on the transaction currency assigned. To set this up, users will require a support ticket requesting for this configuration. Users will then be provided a csv template to populate the bank accounts and their related transaction currency. In a future release, a UI element will be added that will allow users the ability to manually create these relationships.
Improvements
Only Instant Payments
Before the update, when a one-time instant payment is created, we also make a direct debit mandate for future automatic payments (if the Intacct user wants to enable automatic payments). Now, we have allowed for the separate creation of these two mandates, where each mandate is created discretely based on the end customer’s preference. In the GoCardless for Sage Intacct>Customers view, a user will have the option for Payment Method:
DirectDebit + InstantBankPay: If the Invoice transaction currency and Bill To country combination is eligible for Instant Bank Pay, then during the first Invoice Payment for the customer, the system sends Direct Debit instructions for regular Mandate authorization and also initiates an Instant Bank payment request for the first Invoice alone. For future invoice payments, the system checks if a regular mandate is available, and if yes, the system initiates a regular payment request.
DirectDebit: The system validates to check if the customer has a valid Mandate in place, if true, the application will initiate a regular payment request. If not, the system will initiate a Direct Debit authorization request, and once authorized, the system will automatically initiate a regular payment request.
InstantBankPay: The application will always send Instant Bank Pay Authorization requests for all Invoice Payments.'
Submit for Faster Payments Based on Currency and Supported Country by GoCardless
Prior to 1.1, the solution included Instant Payment only by currency. It should also have been looking for country code as well. For example Today faster_payments are supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported only in Germany (EUR). With 1.1, the solution will continue to check the Invoice Currency, and for country check, validate BillTo country from Intacct Invoice.
example: apply faster_payments only if invoice currency is (GBP) and invoice_bill_to_country is “UK”
similarly apply “sepa_credit_transfer” or “sepa_instant_credit_transfer” only if the invoice currency is “EUR” and the invoice_bill_to_country is “DE (Germany)”.
Encrypt Sensitive Data
The solution is now encrypting sensitive data that is being passed from UI to Middleware's backend application.
Encrypt the Login Password from UI and Decrypt it in the Middlewares’s backend application.
Do not pass back sensitive information back to UI when a user/payment account list is requested.
KNOWN ISSUES
Issue with the Pay Now Link at the Top Level. An updated link has been generated and will be updated in the documentation.
APPLIES TO
The entire release was applied to all users of GoCardless for Sage Intacct.
PREREQUISITES AND DEPENDENCIES
User has signed up and created an account within GoCardless for Sage Intacct.
User has access to a GoCardless Account.
Proper permissions for the GoCardless for Sage Intacct Web Services user within Sage Intacct company.
ACTIONS
The improvements and bug fixes included in this update are automatically applied to all GoCardless for Sage Intacct customers’ Intacct Companies, so no further action is necessary. The GoCardless for Sage Intacct User Guide is located in the Help Center. Please consult the Sage Intacct GoCardless for Sage Intacct Upgrade – System Changes and Features document available here. For details on any of the historical GoCardless for Sage Intacct releases, please continue to the next section of this document. The next section provides important information to assist customers on understanding the changes and features added to the GoCardless for Sage Intacct application.