Iterating on the strategy outlined in Azure Usage Holding Pattern, we want to improve the traceability and resilience of billable usage handling. These changes will let us check the status of billable usage remittance in the database (e.g. with gabi), rather than depending on the logs, as well as extending retries for transient issues to AWS integration.

See https://docs.google.com/document/d/1liKSpUL1WIRO_MhUKA7OEmNCx4n8foBRmLQEvDpDz6I/edit#heading=h.9vi5pf4gsqem