Summary
If you are using a payment processor that is not currently integrated with Blue Onion, certain automation and reconciliation features will be limited. Specifically, Blue Onion will not automatically receive data such as fees, refunds, marketing deductions, or settlement metadata from that processor. As a result, payout-level reconciliation and automated general ledger (GL) posting may require manual workarounds.
However, if your order data is captured through platforms like Shopify or Amazon and those integrations are active, key features like revenue recognition and order-level accounting can still function as expected.
What’s Affected When the Processor Isn’t Integrated
When Blue Onion does not receive a direct data feed from your payment processor, the following limitations may occur:
🧾 Fees and Charges May Be Missing
Detailed fee lines will not appear in the Payouts view.
Payout totals may not match accounting journal entries, which can cause discrepancies in reconciliation.
🔄 Payouts Cannot Be Automatically Reconciled to Bank Deposits
Without identifiers like payout_id or disbursement_id, Blue Onion cannot match processor settlements to your bank deposits.
This results in unreconciled transactions or unexpected variances in the cash reconciliation process.
❓ Missing Payment-Type Details
Payment types such as marketing fees, promotional reimbursements, or platform deductions may not be visible.
These entries may be missing entirely or appear as “Unknown.”
⛓️ Partial or Multi-Capture Flows May Be Incomplete
For processors like Stripe that support partial or multiple payment captures, Blue Onion will not be able to fully track these flows.
This can result in “Unknown” or incomplete balance allocations.
📦 Split or Aggregated Settlements Can’t Be Traced
Some processors aggregate or split transactions across payouts.
Without processor-level data, Blue Onion cannot identify which orders correspond to which disbursement.
🛠️ Manual Processes Will Be Required
To ensure accuracy, your team may need to:
Download and upload processor reports manually
Import bank statement files
Adjust journal entries manually in your accounting system
🧮 Journal Entries May Post to “Unknown” Accounts
When Blue Onion lacks metadata such as account type or account ID from the processor, amounts may be assigned to “Unknown” accounts in journal entries.
Why These Limitations Occur
Blue Onion’s reconciliation and accounting automation relies on direct data feeds from payment processors. These feeds provide:
Detailed transaction data
Fees, chargebacks, and refund information
Payout identifiers and metadata
Settlement currency amounts
Without access to this data, the system cannot reliably compute payout values, match them to bank transactions, or generate accurate GL postings.
What Still Works (When Order Data Is Available)
Even without an integrated processor, several key features continue to work if you are using other connected platforms like Shopify or Amazon:
✅ Order Capture and Revenue Recognition
Orders imported from connected platforms still support order-level accounting and revenue recognition (RevRec), even without settlement data.
✅ Manual Reconciliation
While this process isn’t fully automated, it allows teams to reconcile outside the platform by downloading payment data from their processor and order data from Blue Onion, then identifying which transactions should link.
✅ Journal Entry Export
Blue Onion can still generate journal entries that can be exported into your GL system for posting.
Frequently Asked Questions
Can I still recognize revenue without payout data?
Yes. As long as Blue Onion is receiving order and fulfillment data from a supported source (like Shopify), revenue recognition can still run normally.
Is custom integration with my processor possible?
Potentially. Please contact your Customer Success Manager to discuss custom options.