There are various reasons why a store transaction will fail to generate a sales order in HQ. We have a known issue for one which happens once every few weeks, but we cannot replicate it. There's a ticket for that already. There's another issue where sometimes the header level discount amount and the line level discount amounts do not match up - I don't know why. For those, they are easier to identify and fix and I do look for those once a week - although I don't recall having had to fix one since maybe January. Other reasons vary based on posting profile rules and can usually be tracked down and resolved.
Here's my usual approach:
1. Look up the transaction in the Store Transactions page. Here you can see if there's a validation error of any kind (you may need to insert the "Validation status" column into your view. For the purpose of this review, we can look at one of Tiffany's examples - transaction number 20-R20-03-1778275053006...and we can see validation was successful.
2. If there was an error, you could see the error message at that point and it would give you further direction. For example, with the discount mismatch issue the error message tells you there is a discrepancy between the header discount amount and the line discount amount. In this case with this transaction above, since there is no error I would then look up the statement number in Store Financials workspace.
In this case, we can see this statement has not posted yet, and that is helpful.
3. Open up the statement to see any statement-level error messages, and then navigate to the "Aggregated transactions" view from the statement execution details to see which transaction(s) are directly affecting this statement.
4. The error message should give you the context needed to resolve the issue. It can be a number of things - something related to the product itself and a posting profile issue, or a journal issue, or in this case it is a customer account issue:
"While processing the state Customer order invoiced, generic exception encountered in retail statement S-20-053110 in the controller : Posting Posting Sales order: SL-001753995 Item: 25917419 Size=M,Color=Black Summary account for customer account SLI-001297624 in posting profile Default does not exist."
For this, we can see there's a customer issue related to their posting profile. Immediately that indicates the customer likely was created with the wrong customer group type.
5. We now need to look up this customer account (Accounts Receivable > Customers > All Customers), and we can see they do have the wrong customer group assigned. The store level customers should have the customer group "Retail" assigned. From here, you would edit the customer group and then save the changes.
6. After the account has been updated, return back to the statement in the Store Financials workspace and revalidate the transactions from that statement. This will update the transaction in that statement, and the subsequent batch jobs for statement posting and sales order generation (synchronization) will take over.
Your end result will have the sales order generated and the statement posted.