To sync Stripe payments from Event Temple to Mews as deposits, specific configurations are required to ensure payments are recorded correctly for revenue reporting and accounting.
Setting Up Mapping for Accurate Revenue Reporting
Create a Dedicated Accounting Category in Mews:
Example: "Deposit Charges"
Reserved exclusively for prepayments.
Payment Type Mapping:
Map a single payment type (e.g., Stripe) between Event Temple and Mews.
Link this payment type to the deposit accounting category.
Workflow for Syncing Prepayment Invoices
Create and Finalize a Prepayment Invoice in Event Temple:
Mark it as a Prepayment Invoice.
Take the payment via Stripe and finalize so the balance is $0.
Automatic Sync to Mews:
Once finalized, the payment automatically syncs to Mews.
How Payments Appear in Mews:
Posts as a deposit, not a regular payment.
Appears as positive revenue in the Booking’s Payments tab and offsets the final bill, ensuring accurate reporting.
Limitations: Only payments associated with Prepayment Invoices in Event Temple can sync to Mews. Payments on other invoice types (standard or Connected invoices) cannot be pushed.