Billtrust and Brex Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Billtrust and Brex matched by integrating their events and actions. When finance events happen in Billtrust, update the Brex automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Billtrust and Brex

Detailed info you need to know about Billtrust and Brex integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Billtrust

    • Finance
    • 9 triggers
    • 31 searches
    • 32 actions

    B2B accounts receivable and payment automation platform for invoices, collections, and cash application.[5]

  • Brex

    • Finance
    • 4 triggers
    • 59 searches
    • 56 actions

    Corporate cards, spend management and business banking.[6]

How to connect Billtrust to Brex

Set up your Billtrust and Brex integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Billtrust and Brex work in WEXTL?

WEXTL exposes actions and triggers for Billtrust and Brex that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Billtrust triggersBrex actions

Billtrust modules

  • Create a Category Adds a dispute category identified by a unique Code and a Description. Use Default Internal Reason and Default External Reason to link default reasons to the new category.
  • Create a Department Sets up a department for disputes from an external Code and a Description.
  • Create a Dispute Opens a dispute against a document, from the Amount, Account Number and Document Number. Give the reason through Reason, Reason Code, External Reason ID or External Reason Code, and use Assignee to hand the dispute to someone.
  • Create a Dispute Note Leaves a note on a dispute, with Content for the text and a Visibility of Internal or All.
  • Create a Reason Creates a reason with a unique Code, a Description and a Visibility setting. Use Category or Category Code to place it under a category, and Active to turn it on.
  • Create a Resolution Defines a resolution under a Code of your choosing, plus a Description. Turn on Is Valid when the resolution marks the dispute as valid.
  • Create an Assignee Creates an assignee in a department, using the First Name, Last Name and Email of the Person. Use Platform User to link a Billtrust Platform user, and turn on All Updates or Daily Digest to choose which notifications the assignee receives.
  • Delete a Buyer Account Card Clears the account numbers named by Buyer Accounts from the credit card payment restriction.
  • Delete a Category Deletes the dispute category with a matching Category Code.
  • Delete a Department Removes one department from dispute handling in Billtrust.
  • Delete a Department by Code Deletes the department matching a Department Code in your Billtrust dispute setup.
  • Delete a Dispute Deletes a dispute record from the dispute service.
  • Delete a Dispute Note Removes one note belonging to a dispute.
  • Delete a Reason Deletes the reason that matches a Reason Code under the category with the Category Code.
  • Delete a Resolution Removes one resolution from the settings used for disputes.
  • Delete a Resolution by Code Finds the resolution with a given Resolution Code and removes it.
  • Delete a Surcharging Buyer Account Removes the account numbers named by Buyer Accounts from the surcharging restriction.
  • Delete an Assignee Removes an assignee from the list kept by the dispute service.
  • Delete an Assignee by Email Deletes the assignee with a matching Assignee Email within the department that has the Department Code.
  • Delete an Attachment Removes one file attachment from a dispute.
  • Generate a Presigned Upload URL Creates a presigned link for attaching a file to a dispute, using the File Name with its extension and a Visibility of Internal or All. You get back an Upload ID and Upload URL.
  • Get a Buyer Account Card Reads the card payment restriction for buyer accounts, with its Restriction type and Override restriction.
  • Get a Category by Code Fetches a category by its Category Code, with its Description and the default internal and external reasons.
  • Get a Company Score Reads the score of a buyer company by its Company ID. The result has Fibs, Dibs, Credit limit, Bankruptcy flag and Out of business flag.
  • Get a Credit Application Retrieves one credit application by its Application ID, including its Application status, Company, Contact and Trade references.
  • Get a Department Pulls a department by Department Code. The result has its Department ID, Code and Description.
  • Get a Dispute Retrieves a single dispute with its Dispute code, Category name, Reason name, Status and Amount.
  • Get a Dispute Note by ID Fetches one note from a dispute, including its Content and Visibility.
  • Get a Reason Looks up one reason using the Category Code of its category and its own Reason Code.
  • Get a Resolution Finds a resolution by its Resolution Code, returning its Description, Active flag and Is valid setting.
  • Get a Signed Credit Application Fetches the signed copy of a credit application by its Application ID. You get the Envelope ID, the Document name and the base64-encoded PDF as Content.
  • Get a Surcharging Buyer Account Checks the surcharging restriction on buyer accounts, with the Restriction type and the Buyer accounts it lists.
  • Get an Assignee by Email Finds the assignee that has a given Assignee Email, returning the Department ID, Active flag and Person details.
  • Get an Attachment Fetches one attachment from a dispute, with its File name, Download URL and Status.
  • Get Business Units Returns business units with their Business units ID and Display name. Use Limit to bound the number of units returned.
  • Get Disputes by IDs Gets several disputes at once from a list of Dispute IDs. Use Limit to restrict how many disputes are read.
  • Get Notification Settings Reads the dispute notification settings: Allow daily digest, Time zone, Time and Allow all updates.
  • Get the Dispute Audit Log Shows the activity log recorded for a dispute. Use Limit to trim a long log.
  • List Assignees Collects assignees and shows which department each belongs to. Use Department to hide assignees from other departments.
  • List Attachments Shows attachments linked to a dispute, each with its File name, Download URL, Status and Visibility. Use Limit to stop after a set number of files.
  • List Categories Reads dispute categories along with their Code, Description and default reasons. Use Limit to restrict the number of categories listed.
  • List Credit Applications Finds credit applications between a Start Date and an End Date, matched against either Application Status Date or Last Modified. Use Application Status Types to keep only certain statuses.
  • List Departments Brings back departments, each with its Code and Description. Use Limit to keep a large list short.
  • List Disputes Searches disputes by Reason Name, Department Name or Category Name (partial matches work), Status, Assignee or Account Number. Use Sort with a leading minus, such as -CreateDate, to sort descending.
  • List Disputes by Document Numbers Finds disputes for an Account Number that match any of the Document Numbers. Add Status to narrow the results.
  • List Documents for a Credit Application Returns documents filed on a credit application, with a Document ID, File name and Document pre signed URL for each. Use Limit to cap how many documents are read.
  • List Notes Pulls the notes on a dispute, each with its Content, Visibility and Create user.
  • List Notes for a Credit Application Gathers the notes left on a credit application, with a Note ID, Notes text and Audit data for each.
  • List Reasons Returns reasons, listing the Code, Description, Active and Visibility of each.
  • List Reasons by Category Shows the reasons under the category that matches a Category Code, listing the Description and Active setting of each.

Brex modules

  • Archive a Budget Moves a budget into the archive using the v2 budgets endpoint.
  • Archive a Spend Limit Archives a spend limit through the v2 endpoint. Limits made through the older endpoint need Archive a Spend Limit (v1) instead.
  • Archive a Spend Limit (v1) Archives a spend limit that was made on the older v1 budgets endpoint. Spend limits from the v2 endpoint use Archive a Spend Limit.
  • Create a Budget Opens a budget under a Parent Budget, with a Name, Description, Period and Amount. Brex rejects Hard as the Limit Type for budgets, so use Create a Spend Limit for a hard limit. Bound it with Start Date and End Date.
  • Create a Card Issues a card to a Card Owner. A physical card needs a mailing address and a vendor card must be virtual with its own Spend Limit and refresh. Set Limit Type to User to follow the limit of the user.
  • Create a Custom Field Defines a custom field for the Accounting, User, ERP or Travel Group. Use Remote ID to tie it to an ID in an outside system. The ERP group also needs an Accounting Integration.
  • Create a Department Registers a department in Brex, ready for people to be placed in.
  • Create a Location Creates a location in Brex. Create a User and Update a User can then assign users to it.
  • Create a Spend Limit Creates a spend limit with its Name, Period and Base Limit. Use Authorization Type to decline card authorizations once the balance runs out or to allow going over, and Rollover Refresh Rate to set how often unused rolled-over funds reset.
  • Create a Spend Limit (v1) Sets up a spend limit on the older v1 budgets endpoint, from a Name, Parent Budget, Period and Limit. Use Spend Type to control which cards can spend from it and Limit Visibility to set whether members can see the limit.
  • Create a Tax Code (Alpha) Defines a tax code inside an accounting integration, with its Name and percentage Rate. Use Subsidiary IDs to limit it to certain subsidiaries and Remote ID to match the code in your accounting system.
  • Create a Tax Group (Alpha) Groups tax codes under one Name for an accounting integration. The names Not Eligible and Custom are reserved and cannot be used.
  • Create a Title Adds a job title to Brex for users to hold.
  • Create a Transfer Sends an Amount out of a Brex cash account, either to a vendor payment account or to another Brex account through Send To. Use External Memo for wire instructions or the ACH entry description and Description for an internal note.
  • Create a User Registers a person from a First Name, Last Name and Email. Use Manager, Department, Location, Title, Cost Center and Legal Entity to place the user in your organization.
  • Create a Vendor Registers a vendor in Brex under a unique Company Name, in ASCII characters only. Use Payment Accounts to set how it gets paid, by ACH, Domestic Wire or Cheque, and add an Email or Phone.
  • Create an Accounting Integration Links Brex to an accounting system, Campfire, Dualentry, Hanover Park, Inkle or Rillet, through your Vendor Account ID. Turn on Amortization to set up the amortization fields as well.
  • Create an Amortization Template (Alpha) Defines an amortization template for an accounting integration. Use Remote ID to link it to the same template in your accounting system.
  • Create an Incoming Transfer Pulls an Amount from a linked bank account into a Brex cash account, with a Description for internal use. Transfers are in USD.
  • Create Custom Field Values Fills a custom field with up to 1000 values. Each Values entry takes a display Value, and you can link it to an outside system through a Value ID or Remote ID. Enable Disabled to block a value from being picked.
  • Delete a Custom Field Deletes a custom field by removing its definition from Brex.
  • Delete a Department Deletes a department from the organization in Brex.
  • Delete a Location Removes a location from the places Brex users can be assigned to.
  • Delete a Tax Code (Alpha) Deletes a tax code of one accounting integration.
  • Delete a Tax Group (Alpha) Removes a tax group that sits under an accounting integration.
  • Delete a Title Deletes a job title from the titles Brex users can hold.
  • Delete a Vendor Removes a vendor you pay through Brex.
  • Delete an Amortization Template (Alpha) Removes the amortization template of an accounting integration.
  • Delete Custom Field Values Deletes values from a custom field. Use Identify By to say whether the IDs are Brex IDs, Value IDs or Remote IDs.
  • Disconnect an Accounting Integration Disconnects an accounting integration and returns its Status, Vendor and Vendor Account ID.
  • Email a Card Number Emails a secure link to the details of a card, with your Sender Name in the subject of the email. The link works for 30 days unless a different number of days is given. Use Message to include a note.
  • Get a Budget Loads a budget, showing its Name, Description, Parent Budget ID and Owner User Ids.
  • Get a Budget Program Retrieves a budget program with its Budget Blueprints, Existing Budget Ids and Employee Filter.
  • Get a Card Pulls a card, showing its Owner, Status, Last Four and Card Type.
  • Get a Cash Account Reads one cash account and returns its Current Balance and Available Balance.
  • Get a Cost Center Reads one cost center and returns its ID and Name.
  • Get a Custom Field Shows how a custom field is set up: Name, Remote ID and whether it Is Disabled.
  • Get a Custom Field Value Reads one value of a custom field, giving its Value, Remote ID and Updated At.
  • Get a Department Looks up a department, returning its ID, Name and Description.
  • Get a Legal Entity Looks up a legal entity: Display Name, Billing Address, Status and Is Default.
  • Get a Location Reads a location and returns its ID, Name and Description.
  • Get a Spend Limit Loads a spend limit from the v2 endpoint, showing its Name, Parent Budget ID and Status.
  • Get a Spend Limit (v1) Loads a spend limit on the v1 budgets endpoint, showing Name, Creator User ID and Parent Budget ID.
  • Get a Tax Code Shows a tax code for an accounting integration, returning its Name, Rate and Subsidiaries.
  • Get a Tax Group Shows a tax group for an accounting integration, returning its Name, Tax Codes and Subsidiaries.
  • Get a Title Shows one job title with its ID and Name.
  • Get a Transfer Looks up a transfer, showing its Counterparty, Payment Type, Amount and Process Date.
  • Get a Trip Opens a trip, showing its Name, Booker User ID and Status.
  • Get a Trip Booking Reads one booking on a trip, showing its Type, Version and Created At. Turn on Load Custom Fields to include its custom field values.
  • Get a User Loads a Brex user with First Name, Last Name, Email, Status and Manager ID. Turn on Load Custom Fields to add custom field values.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Billtrust and Brex integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Billtrust and Brex on WEXTL®

Claim your 3-day trial to build Billtrust with Brex integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Billtrust and Brex.

How do I connect Billtrust and Brex?

Connect your Billtrust and Brex accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Billtrust and Brex?

Example: when the "Watch Assignees" trigger in Billtrust fires, WEXTL can "Archive a Budget" in Brex. Billtrust has 9 triggers (including Watch Assignees, Watch Attachments, and Watch Categories). Brex has 115 actions (including Archive a Budget, Archive a Spend Limit, and Archive a Spend Limit (v1)). Add filters and transforms between steps when you need them.[1]

Can Billtrust trigger actions in Brex, and Brex in Billtrust?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Billtrust and Brex?

No. Billtrust-to-Brex automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Billtrust integrate with Brex in real time?

Yes. Trigger-based automations start the moment Billtrust (or Brex) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Billtrust + Brex integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Billtrust with Brex?

You can build your Billtrust + Brex automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Billtrust and Brex integration.

  1. Billtrust and Brex integration source code, module specs and credentials implementation.
  2. Our Billtrust and Brex integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Billtrust and Brex, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Billtrust integration information
  6. Brex integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Billtrust and Brex integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Billtrust and Brex, or get started