Beanworks is now called Quadient Accounts Payable Automation by Beanworks, often shortened to Quadient AP.

For Sage users, the new name can raise a few practical questions. Is Beanworks still available? Does anything need to change inside Sage? Who handles support now? Do current customers need to take action?

Most users need a focused account review rather than a major system project. This guide explains the rebrand, the items Sage 100 and Sage Intacct users should check, and what companies evaluating the software today need to know.

Is Beanworks Still Available?

Yes. Beanworks continues as the technology behind Quadient’s accounts payable automation product.

Quadient announced its agreement to acquire Beanworks in March 2021. On November 7, 2022, Beanworks became Quadient Accounts Payable Automation by Beanworks.

You may now see several names used for the product:

• Quadient Accounts Payable Automation by Beanworks
• Quadient AP Automation by Beanworks
• Quadient AP by Beanworks
• Quadient AP
• Beanworks

The wording can vary across product pages, login portals, contracts, support materials, and older company documents.

That explains why a user may sign into a portal that still mentions Beanworks while receiving newer communication under the Quadient name. The name changed, and the Beanworks identity remains visible across parts of the product.

What Changed and What Stayed the Same for Sage Users

The primary change is the product branding.

Users may see Quadient listed in places that previously said Beanworks, including sales materials, invoices, support resources, renewal paperwork, security documents, and customer emails.

Internal documentation may still use the old name. Companies can update those references so finance teams, IT staff, auditors, and new employees understand that Beanworks and Quadient AP belong to the same product history.

A few items may require review.

Product and Vendor Records

Your accounting system or vendor-management platform may still list Beanworks as the supplier. Newer invoices or agreements may reference Quadient.

Finance teams should confirm the correct vendor name, legal entity, contact information, and payment instructions before updating any records.

Login and Documentation References

Employees should continue using the login path approved by their organization.

A new product name does not automatically mean a working bookmark, password, or single sign-on setup needs to change. Verify unfamiliar login requests through a known support contact or implementation partner.

Older instructions may also remain useful. Review the document date, product version, and Sage environment before removing them from your internal resources.

Existing Workflows and Accounting Data

A branding update does not automatically require companies to:

• Replace Sage 100 or Sage Intacct
• Rebuild invoice workflows
• Re-enter vendor records
• Recreate approval rules
• Move historical AP documents
• Change integration credentials
• Begin a new implementation

Technical changes may still be needed when a company upgrades Sage, adds an entity, revises its chart of accounts, changes approval authority, or adopts a new payment process.

Those projects should be based on actual accounting requirements and account notices.

Contracts, Licensing, and Support

Subscription terms, product access, billing arrangements, and support responsibilities can differ by customer.

Review your current agreement and renewal documents before assuming that every commercial or support detail remained the same. Confirm anything unclear with Quadient, BCS ProSoft, or the partner responsible for your implementation.

Once those account-level details are clear, the next question is how the product fits with each Sage environment.

Does Quadient AP Still Integrate With Sage?

Yes. Quadient currently promotes accounts payable automation connections for Sage products, including Sage Intacct and Sage 100.

The exact setup depends on the accounting platform, system version, modules, company structure, and AP workflow.

Quadient AP and Sage Intacct

A Sage Intacct connection may involve:

• Vendor records
• General ledger accounts
• Entities
• Locations
• Departments
• Dimensions
• Invoice coding
• Approval rules
• Purchase orders
• Payments
• User permissions

These items should be mapped around the company’s existing Sage Intacct structure.

A multi-entity organization may require more detailed rules than a single-entity business. Companies using custom dimensions or complex approval paths may also need additional configuration.

The implementation team should document which system owns each record, how AP data moves, and how errors are handled.

Quadient AP and Sage 100

Sage 100 environments can vary based on version, hosting, installed modules, custom fields, and third-party modifications.

Before making changes, review:

• The Sage 100 version
• The hosting arrangement
• Accounts payable modules in use
• Vendor and general ledger structures
• Import and export procedures
• Custom fields or scripts
• Approval requirements
• Payment processes

This review helps the implementation team understand what the connection needs to support and where custom work may affect the project.

Existing users can use the same system-specific details to review the health of their current setup.

What Sage Users Should Check Now

A focused account review can identify most rebrand-related issues without disrupting a working AP process.

Confirm the Product Name on Your Account

Check recent contracts, renewal documents, invoices, and vendor records.

Your organization may have records under Beanworks, Quadient, or Quadient AP by Beanworks. Confirm which names appear in current documents and whether any vendor records need to be updated.

Test Your Approved Login Path

Confirm that employees can access the platform through the company’s saved bookmark, password manager, or single sign-on application.

Do not change credentials or use a new login link based only on an unfamiliar email. Verify the request through an established contact.

Verify Your Support Contact

Document where users should go when they need help.

Depending on the account, the first contact may be:

• Quadient
• BCS ProSoft
• Another implementation partner
• An internal Sage administrator
• An internal IT contact

Employees should also know who handles product questions and who handles Sage integration issues.

Identify the Integration Owner

Assign responsibility for the connected AP environment.

That owner should know who monitors:

• Failed imports
• Export errors
• Vendor synchronization
• General ledger mappings
• Entity and dimension records
• Approval routing
• User access
• Integration credentials
• Sage upgrades

Clear ownership helps prevent issues from sitting unresolved between multiple vendors and internal teams.

Review Vendor and Security Records

Check records where the old name could create confusion.

These may include:

• Approved software lists
• Vendor-management systems
• Cybersecurity questionnaires
• Data-processing inventories
• Business continuity plans
• AP procedure manuals
• Training materials
• Audit documentation

Keep the Beanworks name where it helps employees understand the relationship between older and current terminology.

Check Contract and Billing Communications

Review current subscription, billing, and renewal information.

Confirm who receives notices and verify any new payment instructions through an established channel. Standard payment controls still matter during a company or product rebrand.

Leave Working Configurations Alone Until They Are Reviewed

Do not change a connector, URL, credential, field map, or approval rule solely because the product has a new name.

Confirm that a technical change is required before altering the setup.

Is There a Deadline?

Quadient has not published one universal action deadline for every Sage customer.

Any required date should come from a current agreement, authenticated account notice, renewal document, support case, or implementation partner. Companies that have received no specific deadline can complete this review through their normal vendor and software-management process.

The review may also show that a larger technical question needs attention.

When Should You Contact Your Sage or Quadient AP Partner?

Some issues can be resolved through documentation updates. Others require someone who understands the Sage configuration and the AP workflow.

Contact your partner when:

• Users can no longer access the platform
• A Sage import or export stops running
• Vendor or general ledger records no longer match
• Sage Intacct dimensions fail to populate correctly
• Approval routing changes unexpectedly
• The company is planning a Sage upgrade
• New entities, locations, or departments are being added
• Internal teams do not know who owns the integration

A partner can help identify where the issue begins.

An invoice may fail because of missing Sage data, an invalid field value, an AP configuration, a permission setting, or an integration process. Finding the source allows the correct team to address it.

These same technical questions also matter for companies researching the product for the first time.

What Should You Do If You Are Evaluating Beanworks Today?

Companies researching Beanworks will encounter both old and current product names.

Older reviews, articles, and videos may refer to Beanworks. Newer vendor materials may use Quadient AP, Quadient AP Automation, or Quadient AP by Beanworks.

Treat those names as part of the same product history during your research. Base the final decision on the current offering and your current Sage environment.

Ask for recent documentation and a demonstration that reflects the accounting system your company uses.

For Sage Intacct, the demonstration should address entities, dimensions, vendors, invoice coding, and approvals. For Sage 100, it should account for system version, modules, hosting, and custom work.

Use these eight questions during the evaluation:

1. Which Sage products and versions does the proposed connection support?
2. How does data move between Quadient AP and Sage?
3. Which system owns vendor, general ledger, and dimension records?
4. How are failed imports or sync errors reported?
5. Which invoice and purchase order workflows are included?
6. Who configures approval rules and user permissions?
7. Who supports the connection after implementation?
8. How will Sage upgrades or existing customizations affect the setup?

These questions keep the evaluation grounded in the product currently being sold and the accounting process it needs to support.

The implementation partner can then connect those answers to the company’s day-to-day accounting requirements.

How BCS ProSoft Supports Beanworks and Quadient AP Users

BCS ProSoft helps companies connect AP automation with their Sage accounting environment.

That work may involve an existing Beanworks or Quadient AP setup, a new implementation, or a connection that is no longer producing the expected accounting results.

BCS ProSoft can help with:

• Reviewing the current Sage and AP setup
• Planning and configuring the integration
• Mapping vendors, accounts, entities, and dimensions
• Building approval workflows and user permissions
• Investigating import, export, and synchronization errors
• Planning changes for Sage upgrades or new entities

The quality of the setup depends on how well the AP process reflects the company’s accounting structure, approval authority, transaction volume, and reporting requirements.

An implementation partner brings those pieces together and gives finance, IT, Sage, and Quadient contacts a shared plan.

The Bottom Line for Sage Users

Beanworks is now part of the Quadient AP product family, and both names may still appear across portals, documents, and internal records.

Existing Sage users should review their login path, support contact, contract details, billing records, and integration ownership. They should leave working technical settings in place until a verified change is required.

Companies evaluating the product should research both Beanworks and Quadient AP, then judge the current offering based on their Sage environment and implementation needs.

BCS ProSoft can help clarify the setup, correct issues, and plan the next phase of the AP process.

Key Takeaways

• Beanworks is now called Quadient Accounts Payable Automation by Beanworks, often shortened to Quadient AP.
• Existing Sage 100 and Sage Intacct users usually do not need a new implementation because of the rebrand alone.
• Sage users should review login access, support contacts, contracts, billing records, and integration ownership.
• Quadient AP still supports Sage environments, but the setup depends on each company’s version, modules, mappings, workflows, and customizations.
• Companies researching Beanworks today should evaluate the current Quadient AP product and confirm who will handle implementation and ongoing support.

Frequently Asked Questions