FAQs and How-tos
How to understand the invoice grace period in Amberflo
3 min
the invoice grace period in amberflo allows extra time after the end of a billing period to continue ingesting meter events before the invoice is finalized this ensures that delayed but valid usage data—especially from third party platforms—is included before the invoice is locked and sent for payment purpose of the grace period the grace period is primarily useful in scenarios where there’s a delay between when the usage occurs and when it is accurately reported this is common when pulling data from cloud providers such as aws azure google cloud platform (gcp) these platforms typically have an hourly reporting interval a 2–3 day delay before usage records are fully finalized the grace period accounts for this lag, ensuring invoices include complete and accurate data before they are sent to the customer configuring the grace period to configure the invoice grace period go to the amberflo navigate to integrations → connectors → catalog → stripe choose the desired amount of grace time between the billing period end and invoice finalization note amberflo is actively working to decouple this setting from stripe in the future, you will be able to access it globally via settings → invoicing & portal → invoices how de duplication works during grace period if meter events are updated during the grace period make sure to use the same timestamp and same dimensions as the original event amberflo will automatically de dupe the event and retain the latest versio n of the meter value for that timestamp/dimension pair 📘 faqs and how tos docid\ bq14rede1rrwst00mbikx more from invoicing, billing, and payments how to bill customers in different currencies docid\ w2iaparrkbxzneuvoww2x how to resolve when a customer is issued an invoice but has not yet provided payment information docid\ ramjygdjkdlzdnmpfw1kj how to set up your stripe integration in amberflo docid\ p6cy2livo gyeqjrukwo2 how to streamline/automate usage based billing for serverless functions running across multiple cloud envioronments docid\ fejhok8idw46htjkpj3kw
