The Ultimate Invoice
Schema Generator
A statement of the money due for goods or services; a bill.
Magic Build
Paste your URL below and our AI will automatically fill the Invoice fields for you.
Configuration
Live GeneratorWhy use Invoice?
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is Invoice Schema?
A statement of the money due for goods or services; a bill.
Google uses Invoice structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add Invoice Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement Invoice JSON-LD
Generate
Use the form above to fill in your details and generate valid Invoice JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
Invoice schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| accountId | The identifier for the account the payment will be applied to. | Text | Optional |
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| alternateName | An alias for the item. | Text | Optional |
| billingPeriod | The time interval used to compute the invoice. | Duration | Optional |
| broker | An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred. | Organization, Person | Optional |
| category | A category for the item. Greater signs or slashes can be used to informally indicate a category hierarchy. | CategoryCode, PhysicalActivityCategory, Text, Thing, URL | Optional |
| confirmationNumber | A number that confirms the given order or payment has been received. | Text | Optional |
| customer | Party placing the order or paying the invoice. | Organization, Person | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| disambiguatingDescription | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. | Text | Optional |
| identifier | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details. | PropertyValue, Text, URL | Optional |
| image | An image of the item. This can be a URL or a fully described ImageObject. | ImageObject, URL | Recommended |
| mainEntityOfPage | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details. | CreativeWork, URL | Optional |
| minimumPaymentDue | The minimum payment required at this time. | MonetaryAmount, PriceSpecification | Optional |
| name | The name of the item. | Text | Required |
| owner | A person or organization who owns this Thing. | Organization, Person | Optional |
| paymentDue | The date that payment is due. | DateTime | Optional |
| paymentDueDate | The date that payment is due. | Date, DateTime | Optional |
| paymentMethod | The name of the credit card or other method of payment for the order. | PaymentMethod, Text | Optional |
| paymentMethodId | An identifier for the method of payment used (e.g. the last 4 digits of the credit card). | Text | Optional |
Example Invoice JSON-LD
Here's what valid Invoice structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "Invoice",
"name": "Example Invoice",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"accountId": "Example accountId",
"additionalType": "Example additionalType",
"alternateName": "Example alternateName",
"billingPeriod": {
"@type": "Duration"
},
"broker": {
"@type": "Organization",
"name": "Example Organization",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
}
}Validate Your Invoice Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your Invoice schema for errors and Rich Result eligibility