# Developer docs

# Terms

**Seller** - The seller of the receivable.
**Factor** - Who purchases the receivable.
**Debtor** - Paying the receiveable.

Factor percentage -
Commission - The total fee for the liquidity

# Undecided
* Should we create an invoice system?
* Can we use https://www.circle.com/en/developers for payments?

# Assumptions and clearifications
*

## Data

### Invoice (secret info)
date of sale
seller name
seller uuid
invoice number (immutable)
TAX info
Description of items or service
Time and place of delivery of items or service
price with tax
total price
Payment terms (if you gonna sell the invoice, payment terms must be set by exchange)

### InvoiceSale (public info)
**Factor percentage** - When a seller puts up invoice for sale the seller sets a percentage of invoice total for sale and the other percentage which will be locked (be be looked upon as leverage / collateral).

### Customer
* Type
* Number
* TAX
* Address
* Contact

## Pages
* Customers
* Create customer
* 

* Create invoice
* 

* Sell invoice
*
* Buy invoice

## Payment

Invoices are probably denominated in a stable currency. But can be payable in another.

There are different need for payments.

### Sold invoice
An actor has sold an invoice an need money quik in its local currency. That could be FIAT, ETH, DAI etc. Crypot payments are easy. We could provide an escrow service for FIAT payments. So if the

Can we use https://app.mooni.tech/exchange

# Future ideas
* Create EHF service (https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder/ehf-elektronisk-handelsformat).
* A JSON to EHF parser with the possibility to factor the invoice.
* An EHF distribution point where you caa factor invoice.
* Plugins for SAAS accounting firms