Collecting invoices from websites and services automatically · Issue #196 · WICG/proposals · GitHub

//voltron/issues_fragments/issue_layout" data-turbo-transient="true" />

Skip to content

Search/

Sign in<br>Sign upAppearance settings

You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

{{ message }}

Uh oh!

There was an error while loading. Please reload this page.

WICG

proposals

Public

Notifications<br>You must be signed in to change notification settings

Fork<br>31

Star<br>297

Collecting invoices from websites and services automatically #196

New issue<br>Copy link

New issue<br>Copy link

Open

Open<br>Collecting invoices from websites and services automatically#196

Copy link

Description

collimarco<br>opened on Feb 5, 2025

Issue body actions

Introduction

If you have a company and you need to collect all the invoices (e.g. PDF) from different websites and services for accounting reasons, that may take a lot of time. It's especially time consuming if you have many recurrent invoices (e.g. monthly invoices from many different services).

Downloading the invoices (e.g. PDF) from all the websites takes a lot of time. Some websites send the invoices by email, some websites don't and everyone does it in a different way.

I propose a simple protocol to collect the invoices automatically.

Proposed Solution

Let's say that company Alpha is a customer of company Beta. Sometimes Beta needs to send a PDF invoice to Alpha.

Alpha logs in to the dashboard of the service provider Beta and in the billing section adds a URL like:

https://example.com/collect/invoices/LONG_RANDOM_TOKEN

Then Beta can send a normal HTTP POST request with the PDF file (or any other format) whenever generates a new invoice (beside other methods like sending the PDF by email, which can coexist).

Alpha uses the normal HTTP status codes for a semantic response.

Alpha gives a URL with a different LONG_RANDOM_TOKEN to each authorized service, so that they can be sure about the origin of the request.

Privacy & Security Considerations

No considerable privacy or security concerns are expected, but we welcome community feedback.

Reactions are currently unavailable

Metadata<br>Metadata<br>Assignees

No one assigned

Labels

No labelsNo labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions<br>Open in GitHub Copilot app

You can’t perform that action at this time.