Migrate from PayTraq to Infor CloudSuite Corporate

PayTraq's standard GL account structure (Asset, Liability, Equity, Revenue, Expense) maps directly to Infor CloudSuite's Chart of Accounts. We preserve account codes, account types, and cost-center tagging. This migration must complete before any Journal Entries, Invoices, Fixed Assets, or Loan records load because Infor enforces GL account referential integrity. Account groups and cost-center hierarchies map to Infor's dimension structures.

PayTraq Client records map to Infor CloudSuite Customer or Business Partner depending on the CloudSuite edition deployed. We preserve currency assignment, payment terms, and tax ID. PayTraq's CSV import matching by client code or name becomes Infor's party ID with a customer-specific alternate ID. Clients must load before any open Invoice records referencing them.

PayTraq Supplier records map to Infor CloudSuite Vendor or Supplier. Purchase terms, currency, payment terms, and tax ID transfer. Supplier records must load before any Purchase Order or AP voucher records referencing them. We merge supplier price lists into Infor's vendor-managed pricing tables where the destination edition supports it.

PayTraq Products and Services use separate CSV templates. We merge them into Infor CloudSuite's Items table, handling unit-of-measure conversions and cost/sell price fields. Service items get flagged as non-inventory items in Infor. Product code from PayTraq's hs_sku equivalent becomes the Infor Item Number. Price lists from both Products and Services merge into Infor's price tables.

This is the highest-risk object in the migration. PayTraq has no bulk export or import workflow for warehouse items, so we read current on-hand quantities per product-warehouse combination via the API individually. This is slower than a flat export but preserves all on-hand quantities and warehouse assignments. Multi-warehouse configurations require sequential per-warehouse reads within the 5,000-request daily API cap, which may require multiple migration sessions.

PayTraq Sales Invoices map to Infor CloudSuite AR Invoices. We map invoice headers and line items together, preserving tax rates and discount amounts. Multi-currency invoices require the exchange rate at invoice date to be carried forward as Infor requires that rate for currency revaluation. Invoices must load after Clients and Products. Open invoices load fully; historical closed invoices load as posted records.

PayTraq Purchase Orders map to Infor CloudSuite Purchase Orders. PO headers and lines migrate with Supplier and Product references resolved via the mapping already established in the Supplier and Product loads. Partially received POs are flagged because Infor handles partial receipt recording differently depending on the receiving workflow configuration.

PayTraq Journal Entries map to Infor GL Journal Entry records with debit/credit lines mapped to GL accounts. This object must load after the Chart of Accounts is established. We skip Journal Entries linked to prepaid expense schedules or financial loans and flag them for manual review because those GL accounts have destination-specific dependencies that cannot be resolved automatically. Multi-currency journal entries carry the exchange rate at entry date.

PayTraq Employee records map to Infor CloudSuite Workers or Users depending on the CloudSuite edition. We preserve compensation fields and effective dates for payroll history where Infor's data model supports it. Employee records are typically loaded before Journal Entries if the entries reference payroll-related GL accounts.

PayTraq Fixed Asset records (acquisition cost, depreciation schedule, linked GL accounts) map to Infor Fixed Assets. We flag depreciation methods and accumulated depreciation fields for manual verification because Infor's depreciation engine may apply conventions (straight-line, declining balance, units of production) differently depending on the asset category configuration. Acquisition date and cost transfer; the depreciation schedule is reconstructed from the source data and entered manually or via Infor's fixed asset import.

PayTraq Financial Loans are tracked as separate records linked to GL accounts. We do not map to a native loan object because Infor CloudSuite does not have a generic loan record type across all editions. Instead, we create recurring journal entry templates for principal and interest payments and flag the loan ID reference for manual reconciliation. The customer's accountant reviews the amortization schedule and confirms GL account assignments in Infor post-migration.

PayTraq tax rates and tax codes referenced on invoices map to Infor CloudSuite's tax configuration. We note that Infor may require separate tax agency setup for each jurisdiction that the customer operates in, which must be done manually in Infor's tax module after migration. Tax codes load before any invoice or journal entry records.