We are currently not pruning remittance records and they will continue to grow over time. Once we start storing historical remittance, the number of records will increase at a faster pace. We should create a job that will purge remittance records when they reach a configurable age.

To accomplish this:

• Implement a method on BillableUsageRemittanceRepository that will delete remittance records based on a max age duration
• Add an internal RPC API endpoint to the internal-tally-api-spec.yaml and implement it so that it starts an asynchronous process to purge remittance.
  • HOURLY remittance should be purged based on a max daily retention policy (aligned with hourly tally retention policy)
  • DAILY remittance should be purged based on a max hourly retention policy (aligned with daily tally retention policy)
• Configure a curl based scheduled job that makes a request to the new API to start the purge process.