Xoxoday Plum supports separate cash deposit accounting per project, study, or record using a parent/child account structure that keeps each program’s funds isolated while giving administrators consolidated visibility from a single dashboard.
Separate deposit accounting across multiple programs
Xoxoday Plum’s financial architecture is built around a parent/child account model. The parent account holds top-level budget authority and platform-wide visibility, while each child account maps to an individual project, study, or incentive record. Deposits credited to one child account remain fully isolated from others, preventing unintended fund co-mingling across programs. This structure is especially valuable for research institutions and universities running concurrent participant studies funded by separate grants. Each study receives its own deposit pool, draws down independently, and produces a clean audit trail — all without manual separation work from the finance team.How the parent/child model works in practice
When a finance team loads funds into Xoxoday Plum, they allocate specific amounts to designated child accounts at the time of deposit. A university managing three independent clinical trials, for example, assigns a separate deposit balance to each trial. Researchers and program leads access only their allocated funds, while the finance office retains consolidated visibility across every child account from the parent dashboard. Enterprises using ERP systems such as SAP SuccessFactors or Workday can align Xoxoday Plum’s child accounts directly with corresponding cost centers or project codes. Each transaction carries metadata that maps back to the originating child account, so exports slot into existing accounting workflows without manual tagging or reconciliation overhead.Audit controls and compliance
Every deposit and disbursement at the child-account level is logged with a full timestamped record, supporting both internal audits and external compliance reviews. Xoxoday Plum is SOC 2 Type II certified, meaning the controls governing this financial data are independently verified on an ongoing basis. Admins at the parent level can generate per-project financial reports at any point in the program lifecycle. These reports surface opening balances, incremental deposits, rewards issued, and remaining funds — giving finance teams the documentation required for grant reporting, budget cycles, or board-level reviews without relying on manual spreadsheet reconciliation.Who benefits most from this structure
Organizations managing parallel incentive programs get the most immediate value: academic research bodies, contract research organizations, and enterprises running simultaneous employee recognition and channel reward initiatives. Rather than maintaining separate platform accounts for each program — each with its own login, billing cycle, and support relationship — Xoxoday Plum consolidates everything under one account hierarchy while keeping every program’s finances cleanly separated. This model also supports seasonal or project-based incentive campaigns. A marketing team running a quarterly partner incentive alongside an always-on employee rewards program can fund each initiative independently, close out a campaign account when it ends, and carry forward the remaining balance or return it to the parent pool — all within the same interface. Learn more: Xoxoday Plum Help Centre — FinancialSetting budget limits per project account
Learn how to cap spend at the child-account level to prevent budget overruns across concurrent programs.
Exporting transaction reports for reconciliation
Understand how to export itemised deposit and disbursement data from each account for ERP and audit workflows.