Documentation Index
Fetch the complete documentation index at: https://support.pexcard.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Switching your organization’s accounting software affects more than just your general ledger. In PEX, your GL structure lives inside your tag manager — and that tag manager powers your Auto Tagger rules, Auto Enforcer policies, cardholder coding workflows, and accounting integrations. When your chart of accounts changes, each of these areas needs a review.
This article walks you through what to audit, what to update, and in what order — so your team can keep coding and reconciling without interruption.
Two widely used platforms have announced end-of-life dates that may affect your timeline.
QuickBooks Desktop — Intuit is ending support for QuickBooks Desktop in May 2026. If your team currently uses the QuickBooks Desktop integration with PEX, you need to migrate to a supported platform. QuickBooks Online has a native PEX integration available through the PEX Marketplace.
Microsoft Dynamics GP (Great Plains) — Microsoft has announced end-of-life for Dynamics GP in 2029. If you are on this platform, now is a good time to evaluate your migration path. PEX supports Microsoft Dynamics Business Central, which is a natural next step for many GP customers.
If you are mid-migration or evaluating platforms, start the PEX steps in this article as soon as your new chart of accounts is confirmed — not after go-live.
Supported accounting integrations
PEX connects with 50+ accounting, ERP, and productivity platforms at no extra cost. The full list is available at marketplace.pexcard.com. Below are the accounting platforms organized by vertical.
General accounting and ERP
| Platform | Notes |
|---|
| QuickBooks Online | Featured · Nightly transaction imports with receipts; create vendor cards from QuickBooks |
| Oracle NetSuite | Featured · Daily sync with receipts; track against customers, vendors, departments, locations, and classes |
| Sage Intacct | Featured · Sync receipts and transactions for faster reconciliation |
| Microsoft Dynamics Business Central | Featured · Sync PEX receipts and transactions into your Dynamics account for more efficient expense management and reconciliation |
| Xero | Featured · Sync receipts and transactions for faster reconciliation |
| Acumatica | Export transactions for easier expense reconciliation |
| Sage 50 | Export data for small business accounting |
| Sage 100 | Export transactions for mid-sized business finances |
| Sage 300 | Export transactions for multi-entity financial tracking |
| Zoho Books | Sync receipts and transactions to reduce manual bookkeeping |
| Yardi | Export transactions for real estate accounting |
| QuickBooks Desktop | ⚠️ End of life May 2026 — migrate to QuickBooks Online or another supported platform |
Nonprofit and faith-based
| Platform | Notes |
|---|
| Aplos | Featured · Sync PEX with Aplos to reduce reconciliation for nonprofits and churches |
| Blackbaud Financial Edge | Featured · Sync transactions and allocations to populate journal entries automatically |
| MIP Accounting | Export transactions to support nonprofit fund accounting |
| Bloomerang | Export data for nonprofit financial tracking |
| ACS Technologies (Realm) | Convert transactions into ACS Technologies accounting for easier reconciliation |
| Daxko | Convert transactions into Daxko Accounting for easier reconciliation |
| fundEZ | Export transactions for streamlined nonprofit fund tracking |
| ParishSOFT Accounting | Export transactions for simplified church financial reporting |
| PowerChurch Software | Export data for accurate church financial records |
| Serenic Navigator | Convert transactions for easier reconciliation |
| Shelby (ShelbyNext Financials) | Import custom transaction reports tailored for church financial requirements |
| Veracross | Export transactions to streamline school accounting |
Construction
| Platform | Notes |
|---|
| CMiC | Sync transactions into CMiC for expense management |
| Foundation Software | Export data for streamlined construction accounting |
| Procore | Direct connection between PEX and Procore to manage construction expenses and receipts |
| Platform | Notes |
|---|
| Greenslate | Sync transactions for production accounting |
| Extreme Reach (Luca) | Convert transactions into Luca for easier reconciliation |
| Media Services (MediaWeb) | Export transactions in a compatible MediaWeb format for production accounting |
| Wrapbook | Export transactions for production finances |
Expenses and travel
| Platform | Notes |
|---|
| SAP Concur | Featured · Sync PEX transactions into SAP Concur Expense for travel expense management |
| Databasics | Export transactions for easier expense reconciliation |
Productivity and automation
| Platform | Notes |
|---|
| Airtable | Automatically export settled transactions into Airtable |
| Google Drive | Copy cardholder receipts into Google Drive to reduce manual file downloads |
| Google Sheets | Dynamically export settled transactions into Google Sheets |
| Microsoft OneDrive | Copy cardholder receipts into OneDrive to reduce manual file downloads |
| Slack | Get instant transaction alerts and approval notifications in Slack |
| Zapier | Connect PEX with 4,000+ apps available on Zapier |
Before you begin
Complete these three steps before you change anything in PEX.
1. Export your current tag manager
Go to Tags in the admin portal and export your full tag list. This is your source of truth for what is currently mapped to cardholder groups, Auto Tagger rules, and Auto Enforcer policies. Save it.
2. Document your Auto Tagger and Auto Enforcer rules
Open each rule set and note which tags it references. Any rule that uses a GL-mapped tag needs to be updated after you rebuild your tag manager. There is no bulk-export for rules, so document them manually or take screenshots before you make changes.
3. Get your new chart of accounts from Finance
You need the complete, finalized list of GL accounts from your new platform before you touch PEX. Partial lists lead to rework. Confirm with your Finance or accounting lead that the chart of accounts is final and approved.
Step 1: Review your existing tag structure
Open Tags in the admin portal and take stock of what you have.
- Which tags map directly to GL accounts in your current platform?
- Which tags are used for other purposes — departments, projects, locations — that are not tied to GL codes?
- Are any tags assigned to specific cardholder groups or spend categories?
- Are there tags that are no longer used and can be retired?
Tags that are not GL-mapped may not need to change at all. Focus your migration effort on the tags that feed your accounting integration.
Once you have your new chart of accounts in hand, add your new GL codes as tags in PEX.
- Go to Tags in the admin portal and select Add tag.
- Create each new GL account as a tag. Use the same naming convention your accounting platform uses so coding is intuitive for cardholders.
- If your new platform uses a segment structure (department + GL account + location, for example), decide whether to model that as separate tag fields or a combined value. Keep it simple for cardholders — the fewer decisions they need to make at the point of purchase, the better.
- Assign the new tags to the appropriate cardholder groups before you disable the old ones.
Note:Hold off on disabling your old GL tags until your team has finished coding all transactions from the prior period. Cardholders and admins still need those tags to reconcile anything that hit before the switch.
Step 3: Update your Auto Tagger rules
Auto Tagger applies tags to transactions automatically based on merchant, category, or other criteria. If any of your rules reference old GL tags, they need to be updated before the new tags go live.
For each Auto Tagger rule that references a GL tag:
- Open the rule in Auto Tagger.
- Replace the old GL tag with the corresponding tag from your new chart of accounts.
- Confirm the merchant or category criteria still apply under your new platform’s coding structure.
- Save and test with a sample transaction if possible.
Rules that apply non-GL tags (like department or location) typically do not need to change.
Step 4: Update your Auto Enforcer policies
Auto Enforcer flags or blocks transactions based on policy rules — some of which may reference specific tags. Review each policy for GL tag dependencies.
Common areas to check:
- Receipt requirements tied to specific GL accounts or spend categories
- Approval rules that trigger based on how a transaction is tagged
- Spend alerts or flags that reference specific GL values
Update the tag references in each affected policy. If you are restructuring your GL hierarchy significantly, this is also a good time to review whether your policy rules still reflect how your organization wants to manage spend.
Step 5: Reconnect your accounting integration
If you use a PEX accounting integration, you need to reconfigure it after your platform migration. The general steps are:
- Disconnect the existing integration from the Apps section in the admin portal.
- Authenticate and reconnect to your new platform.
- Remap your PEX tags to the corresponding GL accounts in your new chart of accounts.
- Run a test export before your go-live date to confirm transactions are mapping correctly.
For platform-specific setup instructions, visit the help center at support.pexcard.com and search for your accounting platform by name.
Once you have confirmed:
- All prior-period transactions are fully coded and reconciled
- Finance has closed the books for the final period on the old platform
- All Auto Tagger and Auto Enforcer rules have been updated
- Your new accounting integration is tested and working
…you can disable the old GL tags in PEX. We recommend keeping them in a disabled state rather than deleting them. Disabled tags remain visible in transaction history and exports, which helps with audits and any late-period adjustments.
Step 7: Communicate the change to your team
Cardholders and admins notice when the tag list changes. Give them a heads-up before the switch.
For admins: Share the mapping between old and new GL tags, the go-live date, and who to contact with questions.
For cardholders: Keep it simple. Tell them the tag list is changing on a specific date, what the new tags look like, and that the old ones are going away. A one-page reference card with the new GL codes and their descriptions goes a long way.
If cardholders have pending or unsubmitted transactions, ask them to code and submit those before the cutover date — while the old tags are still active.
After the switch: validation checklist
Run through these in the first week after cutover.
Related articles
