A merchant does not obtain authorization for a $30 transaction but sends the clearing message anyway. Galileo is obligated to post all settlements, even if they do not have a matching authorization. This is similar to the transaction shown in <a href="doc:card-transaction-examples#settlement-of-an-expired-authorization" target="_blank">Settlement of an Expired Authorization</a> in _Card Transaction Examples_.

To simulate a force-post, do not create an authorization first and then expire it. In <<glossary:CV>>, you simulate a settlement, and then the simulator creates and backs out an authorization before posting the settlement. This type of transaction is a true force-post, which is transaction type (otype) `M`. Also see:

  • <a href="doc:settlement#driving-an-account-negative" target="_blank">Driving an Account Negative</a> in the _Settlement_ guide — Explains other transactions that are similar to force-postings

  • <a href="page:scenario-19-force-post" target="_blank">Scenario 19: Force Post</a> — A detailed example of a force-post

  • <a href="page:scenario-16-settlement-without-authorization" target="_blank">Scenario 16: Settlement Without Authorization</a> — A settlement arrives after the authorization has expired

### Settlement

Call <a href="ref:post_createsimulatedcardsettle" target="_blank">Create Simulated Card Settlement</a> with these parameters:

`authId`Leave blank
`accountNo`<<glossary:PAN>> or <<glossary:PRN>>
`association``visa` or `mc_auth`
`merchantName``Central Restaurant`

### Transactions created

Call <a href="ref:post_getalltranshistory" target="_blank">Get All Transaction History</a> to see the three ledger entries. When you see an authorization, backout, and settlement with the same timestamp, you know that the transaction was force-posted.